Messages in this thread |  | | Date | Thu, 5 Oct 2000 09:53:10 +0200 | From | Vojtech Pavlik <> | Subject | Re: Status of ReiserFS + Journalling |
| |
On Thu, Oct 05, 2000 at 09:49:29AM +0200, Andi Kleen wrote: > On Thu, Oct 05, 2000 at 09:39:34AM +0200, Vojtech Pavlik wrote: > > Hmm, now that I think about it, this can be brought to data corruption > > even easier ... Imagine a case where a stripe isn't written completely. > > One of the drives (independently whether it's the xor one or one the > > other one) has thus invalid data. > > > > Now how do you decide, after boot, which drive of the set, including the > > xor drive is it the one that contains the invalid data? I think this is > > not possible. > > Normally only the parity block and the actually to be changed block in the > stripe are updated, not all blocks in a stripe set. > > When no disk fails then to be changed block may still contain the old value > after a crash (not worse than the no RAID case). parity will be fixed up to > make the RAID consistent again. The other blocks are not touched.
True, the result is no worse than the normal single disk case.
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |