why does udev set timeout for all SCSI devices? - Kernel
This is a discussion on why does udev set timeout for all SCSI devices? - Kernel ; 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
...
-
why does udev set timeout for all SCSI devices?
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.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
Re: why does udev set timeout for all SCSI devices?
On Thu, Oct 30, 2008 at 03:55, Tejun Heo wrote:
> 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.
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/