In this new systemd timegraph (systemd-time-graph-2.svg) , at the time khaled.service is run, the scheduler had to changed to [none]:
from rc.local Tue Nov 10 03:39:00 UTC 2020 [mq-deadline] none from myscript.sh Tue Nov 10 03:39:08 UTC 2020 [none] mq-deadline The difference between the first time-graph and the second is that khaled.service was moved to after cloud-config.service has *finished* starting-up. I think this basically confirms that something in cloud-config.service is doing (or triggering somehow) this change. ** Attachment added: "systemd-time-graph-2.svg" https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+attachment/5432873/+files/something.svg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
