/boot intermittently fails to mount on boot

Bug #2090972 reported by Krister Johansen
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Status tracked in Plucky
Noble
Fix Released
High
Matthew Ruffell
Oracular
Fix Released
High
Matthew Ruffell
Plucky
Fix Released
High
Matthew Ruffell

Bug Description

[Impact]

Starting on Noble, we see /boot fail to mount in approximately one out
of every two thousand boots. The error looks like this:

   Found device dev-disk-by\x2dlabel-BOOT.device - QEMU NVMe Ctrl BOOT.
   Starting systemd-fsck@dev-disk-by… Check on /dev/disk/by-label/BOOT...
   Checking in progress on 1 disk (0.0% complete)
   Checking in progress on 0 disks (100.0% complete)
   Finished msystemd-fsck@dev-disk-by… Check on /dev/disk/by-label/BOOT.
   Mounting boot.mount - /boot...
   [ 3.051612] /dev/disk/by-label/BOOT: Can't lookup blockdev
   FAILED Failed to mount boot.mount - /boot.
   See 'systemctl status boot.mount' for details.

This has resulted in a number of different failure modes for our users.

Anything that needs to interact with /boot during provisioning will
fail. This is usually something running update-grub or similar.

If we manage to succeed in booting, this can cause subsequent kernel
updates or tools that install kernel modules to fail, because
update-grub fails.

We've _also_ seen this manifest on the root filesystem. In that case,
the boot succeeded, but the by-label links remain absent. When this
occurs, we find installing kernel packages fails because mkinitramfs
can't locate the root disk by label.

[ Testcase ]

It's a vexing problem, and so to reproduce we ran cloud images in a boot
loop until we could reliably reproduce the problem. Unfortunately, we
weren't able to work out anything that made this happen faster, so it's
been a bit slow coming.

It turns out the problem here is that libblkid recently added support to
compute the checksum of the superblocks on ext4 filesystems, and Noble
is the first release to include a version of util-linux new enough to
have this feature. When libblkid determines an ext4 superblock's
checksum is corrupt, it refuses to identify the device as having a
filesystem, which leads to the removeal of the uuid and by-label fields.
systemd-udevd then removes these symlinks. This is where it all goes
wrong.

From our debug traces, it's possible to see this clearly:

(udev-worker)[208]: nvme0n1p16: Probe /dev/nvme0n1p16 with raid and offset=0

systemd-udevd[208]: 208: libblkid: LOWPROBE: [36] ext4dev:
systemd-udevd[208]: 208: libblkid: BUFFER: reuse: off=1024 len=1024 (for off=1024 len=1024)
systemd-udevd[208]: 208: libblkid: LOWPROBE: magic sboff=56, kboff=1
systemd-udevd[208]: 208: libblkid: LOWPROBE: call probefunc()
systemd-udevd[208]: 208: libblkid: BUFFER: reuse: off=1024 len=1024 (for off=1024 len=1024)
systemd-udevd[208]: incorrect checksum for type ext4dev, got D919EB5600000000, expected A47F6CF000000000
systemd-udevd[208]: 208: libblkid: LOWPROBE: [37] ext4:
systemd-udevd[208]: 208: libblkid: BUFFER: reuse: off=1024 len=1024 (for off=1024 len=1024)
systemd-udevd[208]: 208: libblkid: LOWPROBE: magic sboff=56, kboff=1
systemd-udevd[208]: 208: libblkid: LOWPROBE: call probefunc()
systemd-udevd[208]: 208: libblkid: BUFFER: reuse: off=1024 len=1024 (for off=1024 len=1024)
systemd-udevd[208]: incorrect checksum for type ext4, got D919EB5600000000, expected A47F6CF000000000

(udev-worker)[208]: nvme0n1p16: Removing/updating old device symlink '/dev/disk/by-uuid/ce209fd3-a875-4607-9089-35b9de605bd0', which is no longer belonging to this device.
(udev-worker)[208]: nvme0n1p16: No reference left for '/dev/disk/by-uuid/ce209fd3-a875-4607-9089-35b9de605bd0', removing
(udev-worker)[208]: nvme0n1p16: Removing/updating old device symlink '/dev/disk/by-label/BOOT', which is no longer belonging to this device.
(udev-worker)[208]: nvme0n1p16: No reference left for '/dev/disk/by-label/BOOT', removing
(udev-worker)[208]: nvme0n1p16: Successfully created symlink '/dev/block/259:4' to '/dev/nvme0n1p16'
(udev-worker)[208]: nvme0n1p16: sd-device: Created db file '/run/udev/data/b259:4' for '/devices/pci0000:00/0000:00:01.0/nvme/nvme0/nvme0n1/nvme0n1p16'
(udev-worker)[208]: nvme0n1p16: Adding watch on '/dev/nvme0n1p16'
(udev-worker)[208]: nvme0n1p16: Device processed (SEQNUM=1630, ACTION=change)
(udev-worker)[208]: nvme0n1p16: sd-device-monitor(worker): Passed 1315 byte to netlink monitor.

We've also been running with a version of this patch backported to
2.39.3-9ubuntu6.1 in our production environment for a couple of months.
It's completely eliminated this problem for us. We were observing this
about once an hour and have had no recurrence since rolling out the fix.

There are test packages available in the following ppa:

https://launchpad.net/~mruffell/+archive/ubuntu/lp2090972-updates

[Where problems could occur]

We are changing how superblocks are read off of filesystems at initial device
probe time. Luckily, the initial read of the superblock is unchanged from what
happens now. Only if that read fails to compute the correct checksum, then we
read the superblock from the underlying disk with O_DIRECT, and hopefully
compute the correct checksum. If that yeilds an mismatch, then we raise the
incorrect checksum error as usual.

Since this just adds a quick re-read and recompute of the checksum, if a race
between memory and the underlying disk would occur, the recheck would take
minimal amounts of time and would not be noticeable during instance boot time.

If a regression were to occur, it would affect checksum computation, which could
cause the disk to be declared corrupted and not containing a valid filesystem,
which would cause boot to fail, and would have a large impact to users.

[Other Info]

Fortunately, the fix here is straight-forward and is similar to what we
did for resize2fs: use O_DIRECT when reading the superblock. We've
already sent a patch upstream and gotten it accepted there:

commit 483c9f38e377ff0b009f546a2c4ee91a1d61588c
From: Krister Johansen <email address hidden>
Date: Mon, 18 Nov 2024 12:35:22 -0800
Subject: libblkid: fix spurious ext superblock checksum mismatches
Link: https://github.com/util-linux/util-linux/commit/483c9f38e377ff0b009f546a2c4ee91a1d61588c

We had a discussion with Ted Ts'o about this as well, and he had some
ideas for future improvements, but nothing that we're implementing in
this fix:

https://lore.kernel.org/util-linux<email address hidden>/T/#m55eb5087639dcfcfd5708144b1b48caf0cf762b8

Revision history for this message
Krister Johansen (kmjohansen) wrote :
summary: - libblkid: fix spurious ext superblock checksum mismatches
+ /boot intermittently fails to mount
summary: - /boot intermittently fails to mount
+ /boot intermittently fails to mount on boot
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in util-linux (Ubuntu):
status: New → Confirmed
Dave Jones (waveform)
tags: added: rls-nn-incoming
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Matthew Ruffell (mruffell) wrote :

Attached is a debdiff for plucky that solves this issue.

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Attached is a debdiff for oracular that solves this problem

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Attached is a debdiff for noble which solves this issue.

Changed in util-linux (Ubuntu Noble):
status: New → In Progress
Changed in util-linux (Ubuntu Oracular):
status: New → In Progress
Changed in util-linux (Ubuntu Plucky):
status: Confirmed → In Progress
Changed in util-linux (Ubuntu Noble):
importance: Undecided → High
Changed in util-linux (Ubuntu Oracular):
importance: Undecided → High
Changed in util-linux (Ubuntu Plucky):
importance: Undecided → High
Changed in util-linux (Ubuntu Noble):
assignee: nobody → Matthew Ruffell (mruffell)
Changed in util-linux (Ubuntu Plucky):
assignee: nobody → Matthew Ruffell (mruffell)
Changed in util-linux (Ubuntu Oracular):
assignee: nobody → Matthew Ruffell (mruffell)
Revision history for this message
Matthew Ruffell (mruffell) wrote :

Attached is a V2 debdiff for noble

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "libblkid noble patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

I uploaded the patch to plucky:

Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading util-linux_2.40.2-1ubuntu2.dsc: done.
  Uploading util-linux_2.40.2-1ubuntu2.debian.tar.xz: done.
  Uploading util-linux_2.40.2-1ubuntu2_source.buildinfo: done.
  Uploading util-linux_2.40.2-1ubuntu2_source.changes: done.
Successfully uploaded packages.

Is there any way we can validate the fix in plucky before we start the SRU process?

Revision history for this message
Julian Andres Klode (juliank) wrote :

Going to remove the incoming tag as there does not seem to be any action needed here from our side.

tags: removed: rls-nn-incoming
Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Krister,

As Michael Hudson-Doyle mentioned, he has sponsored the new util-linux package
to plucky.

Its currently in -proposed, where it will live for about 24 hours before being
promoted to -release.

https://launchpad.net/ubuntu/+source/util-linux/2.40.2-1ubuntu2

Now Michael is asking if we can do some testing on the plucky package before
I go and upload the packages for oracular and noble.

Is there any chance you could run your testing script against plucky with
2.40.2-1ubuntu1, time how long / how many reboots it took to break and then
re-try with 2.40.2-1ubuntu2 once it gets to -release and see if you can exceed
the numbers from the first run?

How involved is your testing script? Does it do much more than reboot 20,000
times and check the serial console to see if you are lucky enough to get the
race?

You can always upload your script here if you want me to help with testing.

Thanks,
Matthew

Revision history for this message
Krister Johansen (kmjohansen) wrote (last edit ):

Hi Matthew,
I went ahead and put together a plucky cloud image so I can try running the tests against this. I'll report back with the results.

Conceptually, the test just launches a qemu instance and the greps the logs at an interval to determine if it's either booted or hit the bug. If it's booted, the vm is killed, files cleaned up, and we start one again. If it fails, it leaves the VM running in the background so I can poke at it. I can send along the scripts, but the fiddly parts are actually setting up the machine and getting the image in a good state for testing.

When I ran the Noble tests, I went through a few variations and finally settled on an initrd-less UEFI boot with the root device as a virtualized nvme device that gave the best results. I haven't tried to be this fancy with plucky yet, but did clone the uefi + nvme parts (mostly because I already had them handy).

One area where I'm running into trouble with Plucky, but where I didn't with Noble, is getting the nocloud cloud-init working with the networking config. Specifically, my boot times are currently being horked by systemd-networkd-wait-online waiting for something to come online despite the fact that I've only configured loopback. If you know of a way to tell cloud-init to tell networkd that there are no more devices to wait for, I could use a hint there. In the absence of more clever ideas, I'm simply calling the test a success when it reaches the stage before the 2-minute wait, instead of waiting to see the login prompt.

Best,
-K

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package util-linux - 2.40.2-1ubuntu2

---------------
util-linux (2.40.2-1ubuntu2) plucky; urgency=medium

  * Read the ext4 superblock with O_DIRECT if the first read produces a
    checksum failure. This fixes a race where the underlying superblock
    can be changed in memory but not on disk, resulting in checksum
    failures which in turn causes systemd-udevd to remove by-uuid and
    by-label symlinks. (LP: #2090972)
    - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checksum-mismat.patch

 -- Matthew Ruffell <email address hidden> Thu, 05 Dec 2024 13:02:57 +1300

Changed in util-linux (Ubuntu Plucky):
status: In Progress → Fix Released
Revision history for this message
Krister Johansen (kmjohansen) wrote :

Hi Matthew,
A quick update from me on the testing. It took a couple of days to find a recipe that reproduces the problem on Plucky, but I now have a test that's reproduced the issue 4 times in the last 2 days. This isn't as frequently as Noble, where we saw it approx 1:2000 boots in production and 1:56000 boots using a similar synthetic test.

I'll apply the 2.40.2-1ubuntu2 that's been released. Thanks for getting this out quickly. I'll re-run the tests against that, and if we don't see a reproduction in 5 days, are you agreed that we can call this verified on Plucky?

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Krister,

Yes, let's agree that if we don't see the issue in 5 days, its verified for
plucky.

I have noble and oracular packages ready for upload, so let's see if we can get
them on the upload queue Monday or Tuesday for SRU review.

I haven't heard of the cloud-init issue sorry. If you are felling especially
motivated, you can file a bug here: https://github.com/canonical/cloud-init/issues

Lets touch base early next week, and thanks for helping with the testing!

Matthew

Revision history for this message
Krister Johansen (kmjohansen) wrote :

Hi Matthew,
I've been running the tests on the patched version of Plucky since 12/10 and have not observed a recurrence of the bug. In accordance with our previous discussion, I'm going to mark this as plucky-verification-done. (Assuming that's the correct tag). Is this sufficient to unblock the upload of the proposed Noble fix?

Thanks again,

-K

Revision history for this message
Krister Johansen (kmjohansen) wrote :

Ah, there's no verification-done-plucky tag, but if there were, I'd use it.

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Krister,

Thanks for giving plucky a good test. Yes, as agreed, I have now uploaded
util-linux for noble and oracular to the -unapproved queue.

We now need to wait for the SRU team to review the patches, and on acceptance
they will be built and placed into -proposed.

The SRU team is a little thin at the moment, and company end-of-year shutdown
is next week, so this might happen early January.

Let's keep an eye out though.

Thanks,
Matthew

Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Krister, or anyone else affected,

Accepted util-linux into oracular-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util-linux/2.40.2-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-oracular to verification-done-oracular. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-oracular. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in util-linux (Ubuntu Oracular):
status: In Progress → Fix Committed
Changed in util-linux (Ubuntu Noble):
status: In Progress → Fix Committed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello Krister, or anyone else affected,

Accepted util-linux into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util-linux/2.39.3-9ubuntu6.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Krister Johansen (kmjohansen) wrote :

Hi Matthew and Timo,
Thanks for getting the Noble and Oracular proposed packages posted so promptly. I'll go ahead and kick off test runs on these this morning and can follow up by Friday morning (Pacific Time) about whether they have passed. If you don't think that's long enough, I can let them run over the holiday break and can follow up on January, 3rd. I've previously been able to reproduce the problem on Noble within 4 hours on a synthetic test.

Thanks, and hope you have a relaxing holiday.

-K

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (util-linux/2.40.2-1ubuntu1.1)

All autopkgtests for the newly accepted util-linux (2.40.2-1ubuntu1.1) for oracular have finished running.
The following regressions have been reported in tests triggered by the package:

cloud-utils/0.33-1 (ppc64el)
cmake-extras/1.7-3 (amd64)
dpdk/23.11.2-0ubuntu1 (arm64)
freedom-maker/0.33 (ppc64el)
glib2.0/2.82.1-0ubuntu1 (ppc64el)
kdump-tools/1:1.10.3ubuntu4 (ppc64el)
multipath-tools/unknown (ppc64el)
netplan.io/1.1-1 (arm64, ppc64el, s390x)
openjdk-21/21.0.5+11-1ubuntu1~24.10 (s390x)
openjdk-22/22.0.2+9-4 (amd64, ppc64el)
openjdk-23/23.0.1+11-1ubuntu1~24.10.1 (s390x)
openjdk-24/24~16ea-1 (amd64, ppc64el)
openjdk-8/8u432-ga~us1-0ubuntu2~24.10 (amd64, i386)
openvswitch/3.4.0-1 (amd64)
piuparts/1.4.3 (amd64, i386)
python3.12/3.12.7-1ubuntu1 (amd64)
python3.12/unknown (ppc64el)
python3.13/3.13.0-1 (arm64, ppc64el)
rsyslog/8.2406.0-1ubuntu2 (ppc64el)
systemd/256.5-2ubuntu3.1 (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/oracular/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (util-linux/2.39.3-9ubuntu6.2)

All autopkgtests for the newly accepted util-linux (2.39.3-9ubuntu6.2) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

autopkgtest/5.38ubuntu1~24.04.1 (amd64, arm64)
cloud-utils/unknown (ppc64el)
cryptsetup/2:2.7.0-1ubuntu4.1 (arm64)
dpdk/unknown (ppc64el)
fence-agents/4.12.1-2~exp1ubuntu4 (ppc64el)
gsequencer/6.5.2-1build3 (amd64, s390x)
livecd-rootfs/24.04.81 (s390x)
netplan.io/1.0.1-1ubuntu2~24.04.1 (ppc64el, s390x)
nfs-utils/1:2.6.4-3ubuntu5 (ppc64el)
open-iscsi/2.1.9-3ubuntu5.2 (ppc64el)
openjdk-21/21.0.5+11-1ubuntu1~24.04 (s390x)
openjdk-8/8u432-ga~us1-0ubuntu2~24.04 (i386)
openvswitch/3.3.0-1ubuntu3 (amd64, arm64)
rsyslog/8.2312.0-3ubuntu9 (ppc64el)
zfs-linux/2.2.2-0ubuntu9.1 (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Krister Johansen (kmjohansen) wrote :

Just wanted to follow-up to report that I've run the reproducer on Noble and Oracular since the 17th and while I did reproduce the bug on both releases with the old version of the package, I did not see any occurrences with the new versions of the packages. If there are no objections, I'll mark those releases as verified.

tags: added: verification-done-noble verification-done-oracular
Revision history for this message
Krister Johansen (kmjohansen) wrote :

I didn't take an exhaustive look at the reported test failures, but the ones I did look at above appear to be related to the test infrastructure not starting up. Can we give those another kick to see if a subsequent run does any better? Thanks.

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Krister,

Thank you very much for running tens of thousands of boot tests on Noble and Oracular. I'll get onto those autopkgtest failures, let me hit retry.

Hopefully we can get this released once they are all cleared.

Thanks,
Matthew

Revision history for this message
Krister Johansen (kmjohansen) wrote :

Hi Matthew,
Thanks for you help with getting this fixed. Please let me know if there's anything else I can do to assist.

Thanks,

-K

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Krister,

We are just stuck on one particularly stubborn autopkgtest of python3.12 in
oracular.

https://ubuntu-archive-team.ubuntu.com/proposed-migration/oracular/update_excuses.html#util-linux
https://autopkgtest.ubuntu.com/packages/p/python3.12/oracular/amd64

I have hit retry many times, we but we keep hitting infrastructure issues.

Noble is all good, they have all passed:

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#util-linux

I'll try a couple more times, otherwise I will ask to release without this
particular test succeeding.

Thanks,
Matthew

Revision history for this message
Krister Johansen (kmjohansen) wrote :

Hi Matthew,
I appreciate the update and your persistence in prodding these stubborn tests along. Is it okay to release the Noble build of this package ahead of the Oracular one?

Thanks again,

-K

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

The tests are green now.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package util-linux - 2.40.2-1ubuntu1.1

---------------
util-linux (2.40.2-1ubuntu1.1) oracular; urgency=medium

  * Read the ext4 superblock with O_DIRECT if the first read produces a
    checksum failure. This fixes a race where the underlying superblock
    can be changed in memory but not on disk, resulting in checksum
    failures which in turn causes systemd-udevd to remove by-uuid and
    by-label symlinks. (LP: #2090972)
    - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checksum-mismat.patch

 -- Matthew Ruffell <email address hidden> Thu, 05 Dec 2024 13:02:57 +1300

Changed in util-linux (Ubuntu Oracular):
status: Fix Committed → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote : Update Released

The verification of the Stable Release Update for util-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package util-linux - 2.39.3-9ubuntu6.2

---------------
util-linux (2.39.3-9ubuntu6.2) noble; urgency=medium

  * Read the ext4 superblock with O_DIRECT if the first read produces a
    checksum failure. This fixes a race where the underlying superblock
    can be changed in memory but not on disk, resulting in checksum
    failures which in turn causes systemd-udevd to remove by-uuid and
    by-label symlinks. (LP: #2090972)
    - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checksum-mismat.patch

 -- Matthew Ruffell <email address hidden> Thu, 05 Dec 2024 15:26:54 +1300

Changed in util-linux (Ubuntu Noble):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.