Date: Mon, 11 Jul 2005 13:19:15 -0400 From: Martin Cracauer <cracauer@cons.org> To: freebsd-current@freebsd.org Subject: gvinum. A little worse than I thought :-) Message-ID: <20050711131915.A19863@cons.org>
next in thread | raw e-mail | index | archive | help
I understand that gvinum doesn't have documentation yet, and I found a
note "or basic stuff (like creating concatinated volumes) you can use
the vinum documentation and replace 'vinum' with 'gvinum' when you try
things."
But this is going a bit far:
sbin/gvinum(grisu)80# gvinum
gvinum -> help
[...]
info [-v] [-V]
List information about volume manager state.
[...]
gvinum -> info
unknown command 'info'
gvinum -> dumpconfig
unknown command 'dumpconfig'
Also, seperate issue, the geom_vinum kernel module is not unloadable
but the "stop" command tries to do exactly that, and fails.
What the stop command does not do is actually stop or detach anything,
so I am stuck with 3 devices captive in a failed raid5 setup attempt
until I reboot.
gvinum -> stop raid
gvinum: cannot unload geom_vinum: Operation not supported
gvinum -> stop raid.lp0
gvinum: cannot unload geom_vinum: Operation not supported
gvinum -> stop
gvinum: cannot unload geom_vinum: Operation not supported
The detach command, listed in help, is also only triggering a message
that it is unsupported.
But have no fear, I just poked a little deeper into Linux raid (raid5)
and it was way worse :-)
What is a recommended ATA or SATA controller with hardware RAID5 and
the capability to run different RAID levels on different parts of the
disk these days?
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
No warranty. This email is probably produced by one of my cats
stepping on the keys. No, I don't have an infinite number of cats.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050711131915.A19863>