[Group.of.nepali.translators] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: e2fsprogs (Ubuntu Lunar) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2051115] Re: ubuntu pro integration interferes with dist-upgrade prompting
This bug was fixed in the package update-manager - 1:24.04.4 --- update-manager (1:24.04.4) noble; urgency=low * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). -- Nathan Pratta Teodosio Mon, 22 Jan 2024 08:17:25 +0100 ** Changed in: update-manager (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2051115 Title: ubuntu pro integration interferes with dist-upgrade prompting Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: New Status in update-manager source package in Bionic: New Status in update-manager source package in Focal: New Status in update-manager source package in Jammy: New Status in update-manager source package in Noble: Fix Released Bug description: The listing of Ubuntu Pro packages has been introduced in recent versions of update-manager, but as an undesired consequence, in up to date machines unattached to Ubuntu Pro, update-manager stopped prompting to upgrade to a next supported release. Ubuntu Pro packages should be merely an addition to this program and not alter its main behavior. [Test plan] ---> ua detach --assume-yes apt update apt upgrade apt install hello update-manager <--- Instead of listing Ubuntu Pro packages (the hello one, for example, always has a ESM update) that would be installable if the user attached to Ubuntu Pro, the update-manager window should simply do as it did in older versions, namely, state that software is up to date, and, if a newer LTS is available, suggest to the user to update to it. [Where problems could occur] The Pro packages should still be listed as such (i.e. under their own section, "Ubuntu Pro security updates", in the package listing) in case there is at least one upgradable package (as of 'apt list --upgradable'), whether the machine is attached, in which case the Ubuntu Pro section is sensitive, or unattached to Ubuntu Pro, in which case it is insensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2051115/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
