Hi,
On Thu, 16 Nov 2017 07:40:08 +0900 James Bottomley <james.bottom...@hansenpartnership.com> wrote: > On Wed, 2017-11-15 at 17:02 -0500, Alan Stern wrote: > > On Wed, 15 Nov 2017, Jérôme Carretero wrote: > > > > Because with several of these drives / lots of activity / > > occasional > > > > issues, it looks like it will be hard to catch (yes I can use > > > > usbmon). > > > > > > > > - It looks like there is no configurable timeout for USB MSC > > requests. > > > > Perhaps the device is not responding in time and this is why > > it's > > > > reset? > > > > Timeouts are set by the SCSI layer. I believe they are rather long > > (30 seconds, by default). Presumably they are configurable, > > although I would have to do some digging to figure out how. > > They're in /sys/class/scsi_device/<id>/device/timeout I'll use wireshark to check the cause: for sure, the drives are not "timing out" after 30 seconds (indeed the reported value in /sys/class/scsi_device/.../timeout or /sys/block/*/device/timeout), because I see (in dstat) that a disk is busy until the right about the moment where its reset message appears. Is it possible that the SCSI timeout doesn't get set into an USB URB timeout (I'll check by myself, but asking doesn't hurt) ? Thank you, -- Jérôme -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
