>> TLER just shortens the firmware's error recovery from something like >> 60 seconds down to 4 seconds. It's mainly useful in hardware RAID but >> I can see it being useful with mdraid in the enterprise where you >> can't afford to wait for the drive to do it's own recovery attempts. >> >> > This is not correct. You may want to read the ATA8-ACS2 draft standard > (see www.t13.org). There you'll find: SCT-ERC > > The internal error recovery procedure includes a vast amount of > algorithms. If a disk cannot read a sector and starts error recovery, > it may take far more than a minute. > With ERC you can tell the disk beforehand to stop processing the command > (may it be "read" or "write") and return a "uncorrectable error" to the > host. Some drives (i.E. recent Hitachi Deskstar, which I do recommend!) > do not allow you to set ERC lower than 6.5s. And how is that any different from what I said? The observable effect of TLER is the drive giving up after a few seconds instead of a minute or more. Algorithm XYZ and spec ABC of the t13 committee doesn't change what we see. And for most people, the effect is what matters, not how we got there. Myself, I could care less about what goes on under the hood. I enable TLER for HW raid and disable it for regular use. -- Drew "Nothing in life is to be feared. It is only to be understood." --Marie Curie "This started out as a hobby and spun horribly out of control." -Unknown -- 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
