Chris Murphy posted on Tue, 18 Feb 2014 15:02:51 -0700 as excerpted: > Also, what model drives are being used? If they are > consumer drives, they almost certainly have long error recoveries over > 30 minutes.
FWIW, that should be 30 seconds, not 30 minutes (OUCH!). The below context sort of makes that clear for those good enough at reading between the lines, thus the suggestion to change the kernel timeout to 121 seconds, but just in case... > And if the drive is trying to honor the read request for > more than 30 seconds, the default SCSI block layer will time out and > produce messages like what we see here. So you probably need to change > the SCSI block layer timeout. To set the command timer to something else > use: > > echo <value> /sys/block/<device>/device/timeout > > Where value is e.g. 121 since many consumer drives time out at 120 > seconds this means the kernel will wait 121 seconds before starting its > error handling (which includes resetting the drive and then the bus). -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
