[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-10 Thread Khaled El Mously
@David Maybe this should be brought up in the next meeting. I don't think there's more that can be done about this from our side. -- 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

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread Khaled El Mously
>From the google_guest_agent code: google_guest_agent/instance_setup.go: func setIOScheduler() error { dir, err := os.Open("/sys/block") if err != nil { return err } defer dir.Close() devs, err := dir.Readdirnames(0) if err !=

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread Khaled El Mously
With a modified kernel, I was able to determine the name of the process making the change: google_guest_agent Though I'm not really sure why it is making that change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread Khaled El Mously
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.localTue 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

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread Khaled El Mously
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,

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread Khaled El Mously
sda is definitely being registered as mq-deadline .. and it appears to remain that way until quite late in the boot. But then something is changing the sda scheduler later at some point. No luck so far determining what is making that later change. -- You received this bug notification because

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread Khaled El Mously
Strangely: [0.743029] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [0.744256] io scheduler mq-deadline registered -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread David Krauser
@colin-king dmesg output: [0.00] Linux version 5.8.0-1008-gcp (buildd@lgw01-amd64-043) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #8-Ubuntu SMP Thu Oct 15 12:48:27 UTC 2020 (Ubuntu 5.8.0-1008.8-gcp 5.8.14) [0.00] Command line:

[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks

2020-11-09 Thread Colin Ian King
Can you provide the output from dmesg so we can get an idea of what is happening during boot? ** Changed in: linux-gcp (Ubuntu) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu) Status: Triaged => Incomplete ** Changed in: linux-gcp (Ubuntu) Importance: Undecided =>