On Wednesday January 18, gordon@xxxxxxxxxx wrote: > On Wed, 18 Jan 2006, John Hendrikx wrote: > > > I agree with the original poster though, I'd really love to see Linux > > Raid take special action on sector read failures. It happens about 5-6 > > times a year here that a disk gets kicked out of the array for a simple > > read failure. A rebuild of the array will fix it without a trace, but a > > rebuild takes about 3 hours :) > > One thing that's well worth doing before simply fail/remove/add the drive > with the bad sector, is to do a read-only test on the other > drives/paritions in the rest of the set. That way you won't find out > half-way through the resync that other drives have failures, and then lose > the lot. It adds time to the whole operation, but it's worth it IMO. But what do you do if the read-only test fails... I guess you try to reconstruct using the nearly-failed drive... What might be good and practical is to not remove a failed drive completely, but to hold on to it and only read from it in desperation while reconstructing a spare. That might be worth the effort... NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
