Bugzilla – Bug 1216717
suse-module-tools: 60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory
Last modified: 2024-05-31 20:30:03 UTC
Just in case this wasn't reported yet, this error is logged in the journal of a Tumbleweed system with crypto_LUKS devices: Oct 30 15:46:46 localhost (udev-worker)[724]: dm-0: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory Oct 30 15:46:48 localhost (udev-worker)[723]: dm-1: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-1/queue/scheduler}, ignoring: No such file or directory # uname -r 6.5.9-1-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-1/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler Not happening in systems with a similar setup using previous kernel versions: - ALP Dolomite Build6.8 localhost:~ # uname -r 6.4.11-1-default localhost:~ # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue localhost:~ # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler - Leap 15.5 # uname -r 5.14.21-150500.53-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler I don't know if it's a kernel bug or if the udev rule needs to be adjusted.
Thanks for the report. The sysfs attributes "nr_requests", "scheduler", "rq_affinity", "io_timeout", and "wb_lat_usec" are only relevant for request-based queues and have been made invisible with kernel commit 6d85ebf95c44 ("blk-sysfs: add a new attr_group for blk_mq") in kernel v6.5-rc1 and newer.
Created sr#1136446 for suse-module-tools.
This is an autogenerated message for OBS integration: This bug (1216717) was mentioned in https://build.opensuse.org/request/show/1136446 Factory / suse-module-tools
Fixed in suse-module-tools 16.0.42
SUSE-RU-2024:1888-1: An update that has three fixes can now be installed. Category: recommended (moderate) Bug References: 1216717, 1223278, 1224320 Maintenance Incident: [SUSE:Maintenance:34012](https://smelt.suse.de/incident/34012/) Sources used: openSUSE Leap 15.5 (src): suse-module-tools-15.5.5-150500.3.12.2 SUSE Linux Enterprise Micro 5.5 (src): suse-module-tools-15.5.5-150500.3.12.2 Basesystem Module 15-SP5 (src): suse-module-tools-15.5.5-150500.3.12.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-RU-2024:1887-1: An update that has five fixes can now be installed. Category: recommended (moderate) Bug References: 1192014, 1216717, 1217979, 1223278, 1224320 Maintenance Incident: [SUSE:Maintenance:34011](https://smelt.suse.de/incident/34011/) Sources used: openSUSE Leap 15.6 (src): suse-module-tools-15.6.9-150600.3.3.3 Basesystem Module 15-SP6 (src): suse-module-tools-15.6.9-150600.3.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.