Hmm,
the Debian maintainer said it works fine for him.
I OTOH finally got a VM System as well and I can confirm the 30 seconds.
$ cat /sys/block/sd[a-c]/device/timeout
30
30
30
Reverting the udev rule change helps me just as much as it helped you
Timo.
I verified and wonder where these rules are from.
The upstream rules work.
The Debian Rules work (and look nicer)
But ours don't
FYI: current Debian rules:
ACTION=="add", SUBSYSTEMS=="scsi", ENV{DEVTYPE}=="scsi_device",
ATTRS{vendor}=="VMware*" , ATTRS{model}=="Virtual disk*", ATTRS{timeout}=="?*",
ATTR{timeout}="180"
ACTION=="add", SUBSYSTEMS=="scsi", ENV{DEVTYPE}=="scsi_device",
ATTRS{vendor}=="VMware*" , ATTRS{model}=="VMware Virtual S",
ATTRS{timeout}=="?*", ATTR{timeout}="180"
I'll tomorrow sort out where in the merge that was lost and prep a fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790145
Title:
99-vmware-scsi-udev.rules has no effect - timeout by 30 not 180
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1790145/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
