Date: Fri, 12 Dec 2008 11:07:40 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli Message-ID: <ghtd59$ego$1@ger.gmane.org> 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
[-- Attachment #1 --] Ulf Lilleengen wrote: > 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. It doesn't have to be "weird" behaviour, depending on whether gvinum checks parity on reads (does it?). If it does, it will only have to ignore checksum errors in this case. I suppose people will want to run utilities like diskinfo -vt on the volume with invalid parities so it's not a theoretical scenario :) [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJQjfsldnAQVacBcgRAmAkAKDcZeY7tVtgbxu4bpFH/m1m50zj3gCeKL6H PzbmxYNjZHER22QRw/AvMYE= =YTrG -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ghtd59$ego$1>