Date: Fri, 12 Dec 2008 11:03:30 +0100 From: oxy <oxy@field.hu> To: Ulf Lilleengen <ulf.lilleengen@gmail.com> Cc: "Rick C. Petty" <rick-freebsd2008@kiwi-computer.com>, freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli Message-ID: <494236F2.5040803@field.hu> In-Reply-To: <20081212083708.GA1455@carrot.studby.ntnu.no> References: <4940FF0F.2020404@field.hu> <20081211205659.GA72478@keira.kiwi-computer.com> <49419680.4010003@field.hu> <20081212040137.GA76422@keira.kiwi-computer.com> <20081212083708.GA1455@carrot.studby.ntnu.no>
next in thread | previous in thread | raw e-mail | index | archive | help
You mean that after every reboot i have to start the raid5 manually and re-sync? Ulf Lilleengen írta: > On tor, des 11, 2008 at 10:01:37pm -0600, Rick C. Petty wrote: > *snip* > >> There are a set of patches that lulf@ has which I believe put the volume in >> "up" state initially instead of "down", but maybe it only works for >> mirrors. The code in current and RELENG_7 does initially put the volume in >> "down" state. >> >> > Yes, it only works for mirrors, since I thought it doesn't really matter if a > mirror is properly initialized, since the user need to put data into the > mirror for it to be useful anyway. The same goes for RAID-5 I guess, but I > was not sure if it might trigger some weird behaviour since parity would not > match if reading the volume. I will test out a small modification I made, > which removes the need to run 'gvinum start' on the raid5 plexes. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?494236F2.5040803>