Date: Sun, 19 Jul 1998 16:38:59 +0930 From: Greg Lehey <grog@lemis.com> To: Wilko Bulte <wilko@yedi.iaf.nl> Cc: tlambert@primenet.com, gibbs@plutotech.com, andre@pipeline.ch, Matthew.Alton@anheuser-busch.com, Hackers@FreeBSD.ORG Subject: Re: Software RAID-5 performance Message-ID: <19980719163859.H435@freebie.lemis.com> In-Reply-To: <199807152003.WAA03283@yedi.iaf.nl>; from Wilko Bulte on Wed, Jul 15, 1998 at 10:03:32PM %2B0200 References: <19980715094757.P15083@freebie.lemis.com> <199807152003.WAA03283@yedi.iaf.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 15 July 1998 at 22:03:32 +0200, Wilko Bulte wrote: > As Greg Lehey wrote... >> On Tuesday, 14 July 1998 at 20:05:16 +0200, Wilko Bulte wrote: >> 3. As long as the disks didn't physically fail, rebuild the RAID-5 >> set after rebooting. > > I don't think this solves it, as you don't know which block is up to date > and which block is not. Or do I miss your point? Well, you'd have to have some convention like writing the data block before the parity block. Then you could assume that if you found a parity error, the parity block would be wrong, so you could fix it. Of course, any other consistent assumption would work as well, but having the parity block written last would mean you could bring up the array read-only while you were rebuilding it. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980719163859.H435>