[Bug 1833660] Re: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
All three distros are fixed, thanks! What about Eoan? Does it need this fix, too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833660 Title: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833660] Re: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
** Attachment added: "testlog-disco.log" https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+attachment/5306548/+files/testlog-disco.log ** Tags removed: removal-candidate verification-needed verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833660 Title: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833660] Re: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
** Changed in: gce-compute-image-packages (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial ** Attachment added: "testlog-xenial.log" https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+attachment/5306545/+files/testlog-xenial.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833660 Title: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833660] Re: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
Sorry about messing with the status. I should have RTFM twice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833660 Title: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833660] Re: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
Sorry Brian, I managed to miss the original notification. I'll check all 3 distros right now on the GCE. ** Changed in: gce-compute-image-packages (Ubuntu Bionic) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833660 Title: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833660] Re: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
** Attachment added: "testlog-bionic.log" https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+attachment/5306541/+files/testlog-bionic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833660 Title: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.4
Adding a console log text from above because line wrapping made it unreadable in the body of my comment. ** Attachment added: "console-log-python3.6.log" https://bugs.launchpad.net/ubuntu/+source/python3.6/+bug/1835738/+attachment/5290266/+files/console-log-python3.6.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.4
I am not sure if this is the place to report this, but I cannot think of a better one to attract Mathias' attention, sorry. Four python3.6 packages (and likely also python3.7 and python3.8) currently available in the ubuntu-toolchain-r PPA have an unmet version dependency on the 'python3' package. After adding the ppa, apt reports certain packages as upgradeable, but they cannot be upgraded: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic # uname -a Linux [redacted] 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # apt list --upgradable | grep python WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libpython3.6/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] libpython3.6-dev/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] libpython3.6-minimal/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] libpython3.6-stdlib/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3-distutils/bionic 3.6.9-1~18.04 all [upgradable from: 3.6.8-1~18.04] python3-gdbm/bionic 3.6.9-1~18.04 amd64 [upgradable from: 3.6.8-1~18.04] python3-lib2to3/bionic 3.6.9-1~18.04 all [upgradable from: 3.6.8-1~18.04] python3-tk/bionic 3.6.9-1~18.04 amd64 [upgradable from: 3.6.8-1~18.04] python3.6/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3.6-dev/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3.6-minimal/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3.6-venv/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] # apt upgrade --dry-run libpython3.6 libpython3.6-dev libpython3.6-minimal libpython3.6-stdlib python3-distutils python3-gdbm python3-lib2to3 python3-tk python3.6-venv Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-distutils : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed python3-gdbm : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed python3-lib2to3 : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed python3-tk : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed E: Broken packages 'apt show python3 -a' indicates the version 3.6.7-1~18.04 is from 'http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64', and there is also an original distro version 3.6.5-3 that hails from bionic/main. No other sources are available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833660] Re: /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
** Description changed:
Xfer: https://github.com/GoogleCloudPlatform/compute-image-
packages/issues/783
I initially reported the bug there, but it appears the file is owned by
you guys?
I see this bug in Google Cloud images of 18.04 in
--image=ubuntu-1804-bionic-v20190514 --image-project=gce-uefi-images.
What happens is, the image contains the file
/lib/udev/rules.d/99-gce.rules with the following rule:
# Switch to using NOOP as the default scheduler per GCE request
SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*",
ATTR{queue/scheduler}="noop"
The rule matches both devices (/sda) and partitions (/sda1), but the
scheduler is a device property and does not apply to partition. These
lines are logged multiple times during the first boot of the image, when
the partition and the filesystem is grown, and once on every subsequent
boot, once per every partition:
- Jun 3 04:46:49 toy-sec-1 systemd-udevd[1442]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda1/queue/scheduler}
for writing: No such file or directory
- Jun 3 04:46:49 toy-sec-1 systemd-udevd[1438]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda15/queue/scheduler}
for writing: No such file or directory
- Jun 3 04:46:49 toy-sec-1 systemd-udevd[1437]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda14/queue/scheduler}
for writing: No such file or directory
+ Jun 3 04:46:49 toy-sec-1 systemd-udevd[1442]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda1/queue/scheduler}
for writing: No such file or directory
+ Jun 3 04:46:49 toy-sec-1 systemd-udevd[1438]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda15/queue/scheduler}
for writing: No such file or directory
+ Jun 3 04:46:49 toy-sec-1 systemd-udevd[1437]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda14/queue/scheduler}
for writing: No such file or directory
To repro, no GCE necessary; you can boot any VM with the guest using the
virtio driver, drop in this file, and run e. g. parted, or any program
opening the raw device, as it triggers kernel uevents. Start parted, and
the messages are logged. Quit parted, and they are logged again.
This issue is harmless, but when you ingest logs, you'd rather have them
as error-level message free as possible.
I can think of 3 ways to solve this issue:
1. Make the rule not match partitions. I drop-replace this file in all
my images with the following:
- SUBSYSTEM=="block", ENV{DEVTYPE}!="partition", ACTION=="add|change",
+ SUBSYSTEM=="block", ENV{DEVTYPE}!="partition", ACTION=="add|change",
ENV{ID_VENDOR}=="*Google*", ATTR{queue/scheduler}="noop"
2. Since Ubuntu is providing GCE images, kernel command line option
'elevator=none' sets the I/O scheduler to all applicable devices by
default; no udev integration necessary. The default is not locked, so if
anyone needs to change it (e. g. for a physical disk directly attached
to a VM, not a GCE setup but in a local VM it's possible), they can
select a different elevator strategy with udev rules. This is the
setting widely recommended by other Linux-based system, e. g. there is a
RHEL support page recommending that. It obviously a better choice shift
the I/O elevation job to the host, as it handles requests from all
guests, and can prioritize I/O much better, as it has all consolidated
information available at any moment for the physical device actually
doing the block I/O.
- 3. Since these GCE images come with a special kernel build (it has a
- '-gcp' version suffix), the default of none can be simply selected at
- compile time. It also make sense to compile in virtio into the kernel;
- as it is, the device is probed from initramfs. Since all VM boot drives
- are virtio, it is probably a sensible choice to have it compiled-in;
- definitely so for the GCP-specific kernel build.
+ 3. Since these GCE images come with a special kernel build (it has a '-gcp'
version suffix), the default of none can be simply selected at compile time.
[STRIKEOUT]It also make sense to compile in virtio into the kernel; as it is,
the device is probed from initramfs. Since all VM boot drives are virtio, it is
probably a sensible choice to have it compiled-in; definitely so for the
GCP-specific kernel build.[/STRIKEOUT] EDIT: Sorry, just noticed virtio IS
compiled
+ into this kernel. But that was a side note besides the main point.
Thanks, you'll probably know better than me which of these (or maybe
other options I could not think of right now), as you probably
understand all the implications I'm likely unaware of, so I'm just
[Bug 1833660] [NEW] /lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to partitions
Public bug reported:
Xfer: https://github.com/GoogleCloudPlatform/compute-image-
packages/issues/783
I initially reported the bug there, but it appears the file is owned by
you guys?
I see this bug in Google Cloud images of 18.04 in
--image=ubuntu-1804-bionic-v20190514 --image-project=gce-uefi-images.
What happens is, the image contains the file
/lib/udev/rules.d/99-gce.rules with the following rule:
# Switch to using NOOP as the default scheduler per GCE request
SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*",
ATTR{queue/scheduler}="noop"
The rule matches both devices (/sda) and partitions (/sda1), but the
scheduler is a device property and does not apply to partition. These
lines are logged multiple times during the first boot of the image, when
the partition and the filesystem is grown, and once on every subsequent
boot, once per every partition:
Jun 3 04:46:49 toy-sec-1 systemd-udevd[1442]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda1/queue/scheduler}
for writing: No such file or directory
Jun 3 04:46:49 toy-sec-1 systemd-udevd[1438]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda15/queue/scheduler}
for writing: No such file or directory
Jun 3 04:46:49 toy-sec-1 systemd-udevd[1437]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/virtio0/host0/target0:0:1/0:0:1:0/block/sda/sda14/queue/scheduler}
for writing: No such file or directory
To repro, no GCE necessary; you can boot any VM with the guest using the
virtio driver, drop in this file, and run e. g. parted, or any program
opening the raw device, as it triggers kernel uevents. Start parted, and
the messages are logged. Quit parted, and they are logged again.
This issue is harmless, but when you ingest logs, you'd rather have them
as error-level message free as possible.
I can think of 3 ways to solve this issue:
1. Make the rule not match partitions. I drop-replace this file in all
my images with the following:
SUBSYSTEM=="block", ENV{DEVTYPE}!="partition", ACTION=="add|change",
ENV{ID_VENDOR}=="*Google*", ATTR{queue/scheduler}="noop"
2. Since Ubuntu is providing GCE images, kernel command line option
'elevator=none' sets the I/O scheduler to all applicable devices by
default; no udev integration necessary. The default is not locked, so if
anyone needs to change it (e. g. for a physical disk directly attached
to a VM, not a GCE setup but in a local VM it's possible), they can
select a different elevator strategy with udev rules. This is the
setting widely recommended by other Linux-based system, e. g. there is a
RHEL support page recommending that. It obviously a better choice shift
the I/O elevation job to the host, as it handles requests from all
guests, and can prioritize I/O much better, as it has all consolidated
information available at any moment for the physical device actually
doing the block I/O.
3. Since these GCE images come with a special kernel build (it has a
'-gcp' version suffix), the default of none can be simply selected at
compile time. It also make sense to compile in virtio into the kernel;
as it is, the device is probed from initramfs. Since all VM boot drives
are virtio, it is probably a sensible choice to have it compiled-in;
definitely so for the GCP-specific kernel build.
Thanks, you'll probably know better than me which of these (or maybe
other options I could not think of right now), as you probably
understand all the implications I'm likely unaware of, so I'm just
sharing my thoughts on this issue, not preferring any of these.
I did not check other images available from the same GCE project, but
I'm sure if the rule is there, the result will be identical--it's a
kernel thing, and partitions do not have I/O schedulers by design.
** Affects: gce-compute-image-packages (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833660
Title:
/lib/udev/rules.d/99-gce.rules tries to apply 'scheduler=none' to
partitions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1833660/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774794] Re: btrfs-convert executable is not included in btrfs-progs
FWIW, it looks like btrfs-convert is being dropped upstream. I just compiled mine from source, and it crashed after some heavy churning. The package description should be changed though (it explicitly mentions btrfs-convert). Here's a relevant thread: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854489 referring to the note in https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3: “Warning: As of 4.0 kernels this feature is not often used or well tested anymore, and there have been some reports that the conversion doesn't work reliably. Feel free to try it out, but make sure you have backups.” My backtrace was different, but also related to btrfs_reserve_extent(). I also attempted ext4 -> btrfs. I'll post the BT but it's hardly helpful: # btrfs-convert /dev/sdc1 create btrfs filesystem: blocksize: 4096 nodesize: 16384 features: extref, skinny-metadata (default) creating ext2 image file Unable to find block group for 0 Unable to find block group for 0 Unable to find block group for 0 extent-tree.c:2764: alloc_tree_block: BUG_ON `ret` triggered, value -28 btrfs-convert(+0x1c4f6)[0x558cfb6c54f6] btrfs-convert(btrfs_alloc_free_block+0x1ff)[0x558cfb6cabaf] btrfs-convert(+0x14d63)[0x558cfb6bdd63] btrfs-convert(btrfs_search_slot+0x2af)[0x558cfb6bec8f] btrfs-convert(btrfs_csum_file_block+0x48f)[0x558cfb6d0c1f] btrfs-convert(+0xd944)[0x558cfb6b6944] btrfs-convert(main+0x19d1)[0x558cfb6b5df1] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f75d48fcb97] btrfs-convert(_start+0x2a)[0x558cfb6b64da] Aborted ** Bug watch added: Debian Bug tracker #854489 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854489 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774794 Title: btrfs-convert executable is not included in btrfs-progs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-progs/+bug/1774794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
