On 06/27/2016 06:42 PM, Chris Murphy wrote: > Hi, > > Drives with SCT ERC not supported or unset, result in potentially long > error recoveries for marginal or bad sectors: upwards of 180 second > recovers are suggested. > > The kernel's SCSI command timer default of 30 seconds, i.e. > > cat /sys/block/<dev>/device/timeout > > conspires to undermine the deep recovery of most drives now on the > market. This by default misconfiguration results in problems list > regulars are very well aware of. It affects all raid configurations, > and even affects the non-RAID single drive use case. And it does so in > a way that doesn't happen on either Windows or macOS. Basically it is > linux kernel induced data loss, the drive very possibly could present > the requested data upon deep recovery being permitted, but the > kernel's command timer is reached before recovery completes, and > obliterates any possibility of recovering that data. By default. > > This now seems to affect the majority of use cases. At one time 30 > seconds might have been sane for a world with drives that had less > than 30 second recoveries for bad sectors. But that's no longer the > case. > 'Majority of use cases'. Hardly. I'm not aware of any issues here. The problem with SCT ERC (or TLER or whatever the currrent acronym of the day is called) is that it's a non-standard setting, where every vendor basically does its own thing. Plus you can only influence this on higher end-disks; on others you are at the mercy of the drive firmware, hoping you got the timeout right. Can you post a message log detailing this problem? We surely have ways of influencing the timeout, but first we need to understand what actually is happening. Cheers, Hannes -- Dr. Hannes Reinecke Teamlead Storage & Networking hare@xxxxxxx +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg) -- 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
