Skip to contentSkip to conversation

why does udev set timeout for all SCSI devices?

DISCUSSION Tejun Heo 2 participants 2 messages Oct 30, 2008 SCSI

lore
Share & tools
lore

Tejun Heo

author
#0 lore raw

Hello, Kay.

As the $SUBJ says, why does udev set timeout for all SCSI devices? It's the following two rules.

50-udev-default.rules:SUBSYSTEM=="scsi", KERNEL=="[0-9]*:[0-9]*", ACTION=="add", ATTR{type}=="0|7|14", ATTR{timeout}="60" 50-udev-default.rules:SUBSYSTEM=="scsi", KERNEL=="[0-9]*:[0-9]*", ACTION=="add", ATTR{type}=="1", ATTR{timeout}="900"

The appropriate default timeout differs depending on the transport and the type of the attached device, so the above two rules harm more than help. The affect of the above two rules weren't visible for some reason but with recent block layer timeout update, they actually work and cause problems.

Thanks.

Signature · 1 line
tejun
#1 lore raw
Quoted 8 lines · Tejun Heo

As the $SUBJ says, why does udev set timeout for all SCSI devices? It's the following two rules.

50-udev-default.rules:SUBSYSTEM=="scsi", KERNEL=="[0-9]*:[0-9]*", ACTION=="add", ATTR{type}=="0|7|14", ATTR{timeout}="60" 50-udev-default.rules:SUBSYSTEM=="scsi", KERNEL=="[0-9]*:[0-9]*", ACTION=="add", ATTR{type}=="1", ATTR{timeout}="900"

Quoted 5 lines

The appropriate default timeout differs depending on the transport and the type of the attached device, so the above two rules harm more than help. The affect of the above two rules weren't visible for some reason but with recent block layer timeout update, they actually work and cause problems.

It's in there for years, I can not even dig out, where it is coming from. I just removed it from the default rules.

Thanks,
Kay