Re: Announcing: gvirstor

Yoshihiro Ota wrote:

> Reading "gvirstor implementation details", it is not intended to remove components, is it?  If not, it will a grate benefit to allow "take-off" components as some device may go bad while other devices are still functioning when a virstor is created with multiple devices.

If it's a much requested feature, I'll implement it; as it is currently
done, only unused components at the end of the list of components can be
removed.

> I tried it anyway.  It seemed that I was able to detach md3 and then add md4.  Md3 was not used at all when I removed; status only displaed md2 but I was not sure if it was removed perfectly in gvirstor as no mention in the document.  Later, I was not able to add md3 back again.
> 
> These are the command lines I tried
> # mount /dev/virstor/test /mnt/tmp
> # tar xf ports.tar.bz -C /mnt/tmp &
> # ./gvirstor remove test md3

Ok, I'll try this situation at my development machine.

> # ./gvirstor add test md4
> # ./gvirstor status test
> # ./gvirstor add test md3
> 
> Kernel paniced after a while. Many things were going so it was not sure that gvirstor was the cause of the problem.

Kernel panic message may tell you what system panicked.

> I will try as time permitts.

Thank you.