lkml.org 
[lkml]   [2000]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Status of ReiserFS + Journalling
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.


-Andi
-
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/

\
 
 \ /
  Last update: 2005-03-22 12:39    [W:0.074 / U:3.084 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site