lkml.org 
[lkml]   [2007]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: limits on raid
> For raid5 on an array with more than 3 drive, if you attempt to write
> a single block, it will:
>
> - read the current value of the block, and the parity block.
> - "subtract" the old value of the block from the parity, and "add"
> the new value.
> - write out the new data and the new parity.
>
> If the parity was wrong before, it will still be wrong. If you then
> lose a drive, you lose your data.

Wow, that really needs to be put somewhere in 120 point red blinking
text. A lot of us are used to uninitialized disks calculating the
parity-on-first-write, but if linux MD is forgoeing that
'dangerous-no-resync' sounds really REALLY bad. How about at least a
'Warning: unlike other systems this WILL cause corruption if you
forego reconstruction' on mkraid?
-
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/

\
 
 \ /
  Last update: 2007-06-16 06:43    [W:0.176 / U:0.164 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site