Messages in this thread |  | | From | Neil Brown <> | Date | Mon, 22 Jan 2001 17:37:10 +1100 (EST) | Subject | Re: [PATCH] - filesystem corruption on soft RAID5 in 2.4.0+ |
| |
On Monday January 22, inka-user@lina.inka.de wrote: > In article <14955.19182.663691.194031@notabene.cse.unsw.edu.au> you wrote: > > There have been assorted reports of filesystem corruption on raid5 in > > 2.4.0, and I have finally got a patch - see below. > > I don't know if it addresses everybody's problems, but it fixed a very > > really problem that is very reproducable. > > Do you know if it is safe with 2.4.0 kernels to swap on degraded soft raids? > On the debian-devel list there is a discussion. Currently Debisn Systems to > not do swap-on on boot if a raid partition is resyncing.
In 2.2 it was not safe to swap to a RAID array that we being resyched or was having a spare reconstructed, but in 2.4 it is perfectly safe.
It would be entirely appropriate for the init.d script to check for version >= 2.3.9pre8 (I think that is when the new resync code went it) - or probably just >= 2.4.0, and bypass any fancy checks if that is the case.
NeilBrown
> > Greetings > Bernd > - > 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/ - 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/
|  |