Displaying 2 results from an estimated 2 matches for "device_busi".
Did you mean:
device_busy
2018 Jan 31
0
systemd-udevd not applying ATTR to block device at boot
Hi everyone,
I have a udev rule file that contains a singular rule:
SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ENV{DEVTYPE}=="disk", ATTR{queue/scheduler}:="noop"
When I use a Google Cloud instance and boot it, things work as expected and /dev/sda (a persistent disk) uses the noop scheduler. If the instance also has a
2019 Oct 28
3
udev on CEntOS7 - can't get a match, looking for tips...
The mtx binary requires my tape library to be assigned a sg# driver, but
the kernel periodically renumbers the sg devices. Normally, we would
write a udev rule to manually assign a persistent name, but it looks
like things have changed as I can't seem to get a match on CEntOS7. I'd
appreciate any feedback or pointers to help me get my rule working. My
two attempts are below.
cat