Still trying to hunt down who is changing that attribute. It is certainly not a kernel change that is causing this new behaviour. Something in userspace is doing it, very late in the boot.
In the attached systemd time thingie, at the time that both rc- local.service and khaled.service are run, the scheduler was still mq- deadline: from rc.local Tue Nov 10 03:22:15 UTC 2020 [mq-deadline] none from myscript.sh Tue Nov 10 03:22:21 UTC 2020 [mq-deadline] none My guess is that something in cloud-config.service or cloud- final.service is making this change. ** Attachment added: "time thingie showing systemd service times" https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+attachment/5432868/+files/tracing-systemd-1.svg ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
