On 25 November 2014 at 22:34, Phillip Susi <psusi@xxxxxxxxxx> wrote: > On 11/19/2014 7:05 PM, Chris Murphy wrote: > > I'm not a hard drive engineer, so I can't argue either point. But > > consumer drives clearly do behave this way. On Linux, the kernel's > > default 30 second command timer eventually results in what look > > like link errors rather than drive read errors. And instead of the > > problems being fixed with the normal md and btrfs recovery > > mechanisms, the errors simply get worse and eventually there's data > > loss. Exhibits A, B, C, D - the linux-raid list is full to the brim > > of such reports and their solution. > > I have seen plenty of error logs of people with drives that do > properly give up and return an error instead of timing out so I get > the feeling that most drives are properly behaved. Is there a > particular make/model of drive that is known to exhibit this silly > behavior? I had a couple of Seagate Barracuda 7200.11 (codename Moose) drives with seriously retarded firmware. They never reported a read error AFAIK but began to time out instead. They wouldn't even respond after a link reset. I had to power cycle the disks. Funny days with ddrescue. Got almost everything off them. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
