On 5/10/2012 10:26 AM, Marcus Sorensen wrote: > * Using smartctl to increase the ERC timeout on enterprise SATA > drives, say to 25 seconds, for use with md. I have no idea if this > will cause the drive to actually try different methods of recovery, > but it could be a good middle ground. If a drive needs 25 seconds to recover from a read error it should have been replaced long ago. The only thing that increasing these timeouts to silly high numbers does is, hopefully for those doing it anyway, prolong the replacement interval of failing drives. Can anyone guess what the big bear trap is that this places before you? The rest of the drives in the array have been held over much longer as well. So when you go to finally rebuild the replacement for this 25s delay king, you'll be more likely to run into unrecoverable errors on other array members. Then you chance losing your entire array, and, for many here, all of your data, as hobbyists don't do backups. ;) Fist 2 rules of managing RAID systems: 1. Monitor drives and preemptively replace those going down hill BEFORE your RAID controllers or md raid kick them 1a. Don't wait for controllers/md raid to kick bad drives 2. Data is always worth more than disks drives 2a. If drives cost more than your lost data, you're doing it wrong -- Stan -- 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
