Messages in this thread |  | | | Date | Thu, 27 Jan 2005 07:48:39 +0100 | | From | <pcg( Marc)@goof(A.).(Lehmann )com> | | Subject | Re: critical bugs in md raid5 |
On Thu, Jan 27, 2005 at 06:11:34AM +0100, Andi Kleen <ak@muc.de> wrote: > Marc Lehmann <linux-kernel@plan9.de> writes: > > > > The summary seems to be that the linux raid driver only protects your data > > as long as all disks are fine and the machine never crashes. > > "as long as the machine never crashes". That's correct. If you think
Thanks for your thoughts, btw :)
I forgot to mention that even if data is known to be lost it's much better to return, say, EIO to higher levels than to completely shut down the device (after all, this is no differnce to what other block devices behave).
Also, it's still likely that some old error can be repaired, as the broken non-parity block might be old. This is probably better to be handled in userspace, though, with special tools. But for them it might be vital to get the correct disk index, to be able to detect the stripe layout.
It's usually much faster to repair and verify, as opposed to format and restore, of course.
-- The choice of a -----==- _GNU_ ----==-- _ generation Marc Lehmann ---==---(_)__ __ ____ __ pcg@goof.com --==---/ / _ \/ // /\ \/ / http://schmorp.de/ -=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |