Re: critical bugs in md raid5 and ATA disk failure/recovery modes

[Pavel Machek]

Hi!

> > Well, you could set stripe size to 512B; that way, RAID-5 would be
> > *very* slow, but it should have same characteristics as normal disc
> > w.r.t. crash. Unrelated data would not be lost, and you'd either get
> > old data or new data...
> 
> When you lose a disk during recovery you can still lose
> unrelated data (any "sibling" in a stripe set because its parity
> information is incomplete).  RAID-1 doesn't have this problem though.

You are right, I'd have to do soething very special... Like if I know
it is 4K filesystem, raid-5 from 5 disks could do the trick. Like

Disk1		Disk2		Disk3		Disk4		Disk5
bytes0-511	512-1023	1024-1535	1536-2048	parity
....

....no, even that does not work. You could add single bit for each 4K
saying "this stripe is being written" (with barriers etc) and return
read errors if bit is set might actually do the trick, but that's no
longer raid-5... (Can ext3 handle error in journal?)
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/