Public bug reported:
"GCE request" seems to indicate a preference for the 'noop' scheduler,
but w/ a recently created GCE instance using the Ubuntu18 image &
5.3.0-1029-gcp kernel, noop is not an available option (only 'none' and
'mq-deadline' are available). Apparently 5.0 kernels no longer support
non-multiqueue I/O schedulers
(https://kernelnewbies.org/Linux_5.0#Block_layer), so this should be
changed to "none", although for backwards compatibility with pre-5.0
kernels with 'noop' support, some kind of check will be necessary
(unfortunately I'm not familiar enough w/ udev to know if this is
possible within the udev rules file itself, or if it'd have to be done
at the dpkg/config level).
## cat /sys/block/sdb/queue/scheduler
[none] mq-deadline
## cat /lib/udev/rules.d/99-gce.rules
# Give syslog write access to the kernel logs
KERNEL=="console", GROUP="syslog", MODE="0620"
# Switch to using NOOP as the default scheduler per GCE request
SUBSYSTEM=="block", ENV{DEVTYPE}!="partition", ACTION=="add|change",
ENV{ID_VENDOR}=="*Google*", ATTR{queue/scheduler}="noop"
** Affects: gce-compute-image-packages (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- 99-gce.rules attempts to set 'noop' scheduler, which isn't available in
Ubuntu18
+ 99-gce.rules attempts to set 'noop' scheduler, which isn't available in 5.x
kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886391
Title:
99-gce.rules attempts to set 'noop' scheduler, which isn't available
in 5.x kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1886391/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
