Feature suggestion: immediate repair attempt on failed read?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 13/11/2008 23:04, Mikael Abrahamsson wrote (in the "OT: Tips for good hard drives for a home server" thread):
Looking at the md code in linux, would it be possible to do some work around here in that if a drive read operationstalls, let's try to read from the other drives and then re-write the block on the drive that stalled?

I'd like to second this suggestion; my coding skills are WAY too rusty to attempt it myself, but it sounds like an excellent idea.

We could also have a timeout setting so that if a read stalls, at least the application can get its data (by reading the other discs) and the md subsystem can carry on waiting for the read and/or just doing the rewrite in the background.

What happens at the moment - could one slow read cause the array to be switched into degraded mode immediately?

Cheers,

John.
--
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux