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

2005-01-29 Thread 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

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

2005-01-29 Thread Andi Kleen
> 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 unrela

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

2005-01-29 Thread Pavel Machek
Hi! > > The nasty part there is that it can affect completely unrelated > > data too (on a traditional disk you normally only lose the data > > that is currently being written) because of of the relationship > > between stripes on different disks. Well, you could set stripe size to 512B; that way

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

2005-01-27 Thread Marc Lehmann
On Thu, Jan 27, 2005 at 10:51:02AM +0100, Andi Kleen <[EMAIL PROTECTED]> wrote: > > I disagree. When not working in degraded mode, it's absolutely reasonable > > to e.g. use only the non-parity data. A crash with raid5 is in no way > > Yep. But when you go into degraded mode during the crash recov