[Bug 1052770] New: Failed to save IO scheduler settings
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1052770 Bug ID: 1052770 Summary: Failed to save IO scheduler settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: hguo@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 735702 --> http://bugzilla.suse.com/attachment.cgi?id=735702&action=edit y2log The system is a freshly installed KVM running the latest snapshot of tumbleweed. When attempting to change system-wide IO scheduler to noop, this error occurs: Details: Invalid argument @ fptr_finalize_flush - /sys/block/vda/queue/scheduler Caller: /usr/share/YaST2/modules/SystemSettings.rb:252:in `write' lsblk -O output is the following: NAME KNAME MAJ:MIN FSTYPE MOUNTPOINT LABEL UUID PARTTYPE PARTLABEL PARTUUID PARTFLAGS RA RO RM HOTPLUG MODEL SERIAL SIZE STATE OWNER GROUP MODE ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE TYPE DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO WSAME WWN RAND PKNAME HCTL TRAN SUBSYSTEMS REV VENDOR ZONED sr0 sr0 11:0 512 0 1 1 QEMU 1024M runni root cdrom brw-rw---- 0 512 0 512 512 1 noop 128 rom 0 0B 0B 0 0B 1 0:0:0:0 sata block:scsi:pci 2.5+ QEMU none vda vda 254:0 512 0 0 0 64G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline │ 256 disk 0 0B 0B 0 0B 0 block:virtio:pci │ 0x1af4 none ├─vda1 │ vda1 254:1 swap [SWAP] aeec6ca8-628d-49e3-ae58-1daf1c3accc2 0x82 328c4097-01 512 0 0 0 2G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline │ 256 part 0 0B 0B 0 0B 0 vda block:virtio:pci │ none └─vda2 vda2 254:2 ext4 / f871d33d-0b38-4b2d-b9e0-ba204b2bb05e 0x83 328c4097-02 0x80 512 0 0 0 62G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline 256 part 0 0B 0B 0 0B 0 vda block:virtio:pci none -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1052770
http://bugzilla.suse.com/show_bug.cgi?id=1052770#c1
Ladislav Slezák
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1052770
http://bugzilla.suse.com/show_bug.cgi?id=1052770#c2
Howard Guo
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1052770
http://bugzilla.suse.com/show_bug.cgi?id=1052770#c3
Ladislav Slezák
root@g130 /etc/dirsrv # cat /sys/block/vda/queue/scheduler
[mq-deadline] none
I see, the scheduler is not supported by the device. YaST should first check whether it is available. For example on my system the available scheduler combinations are: # cat /sys/block/*/queue/scheduler | sort -u [mq-deadline] none none noop [deadline] cfq noop deadline [cfq] -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1052770
http://bugzilla.suse.com/show_bug.cgi?id=1052770#c4
Ladislav Slezák
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1052770
http://bugzilla.suse.com/show_bug.cgi?id=1052770#c5
Ladislav Slezák
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1052770
https://bugzilla.suse.com/show_bug.cgi?id=1052770#c8
--- Comment #8 from Swamp Workflow Management
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com