Date: Fri, 02 Nov 2007 12:38:36 -0700 From: Peter Giessel <pgiessel@mac.com> To: Joe Koberg <joe@rootnode.com> Cc: Marco Haddad <freebsd-lists@ideo.com.br>, Ulf Lilleengen <lulf@stud.ntnu.no>, freebsd-geom@freebsd.org Subject: Re: gvinum and raid5 Message-ID: <0001DFFC-0115-1000-9A80-3F81219C1B16-Webmail-10013@mac.com> In-Reply-To: <472AA59F.3020103@rootnode.com> References: <8d4842b50710310814w3880f7d3ldf8abe3a236cbcc8@mail.gmail.com> <20071031215756.GB1670@stud.ntnu.no> <472AA59F.3020103@rootnode.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, November 02, 2007, at 01:04AM, "Joe Koberg" <joe@rootnode.com> wrote: >Ulf Lilleengen wrote: >> On ons, okt 31, 2007 at 12:14:18 -0300, Marco Haddad wrote: >> >>> I found in recent researchs that a lot of people say gvinum should not be >>> trusted, when it comes to raid5. I began to get worried. Am I alone using >>> >>> >> I'm working on it, and there are definately people still using it. (I've >> recieved a number of private mails as well as those seen on this list). IMO, >> gvinum can be trusted when it comes to raid5. I've not experienced any >> corruption-bugs or anything like that with it. >> > >The source of the mistrust may be the fact that few software-only RAID-5 >systems can guarantee write consistency across a multi-drive >read-update-write cycle in the case of, e.g., power failure. That may be the true source, but my source of mistrust comes from a few drive failures and gvinum's inability to rebuild the replaced drive. Worked fine under vinum in tests, tried the same thing in gvinum (granted, this was under FreeBSD 5), and the array failed to rebuild. I can't be 100% sure it wasn't a flakey ATA controller and not gvinum's fault, and I no longer have access to the box to play with, but when I was playing with gvinum, replacing a failed drive usually resulted in panics.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0001DFFC-0115-1000-9A80-3F81219C1B16-Webmail-10013>