There is no action needed from a cloud-init point of view, and we do not
see our integration test failing anymore regarding this issue. Daily
cloud images seem to contain the patched kernel. Marking this as invalid
for cloud-init.
** Changed in: cloud-init (Ubuntu Jammy)
Status: Confirmed => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2003816
Title:
Regression in ext4 during online resize
Status in cloud-init package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-gcp package in Ubuntu:
Invalid
Status in cloud-init source package in Jammy:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-aws source package in Jammy:
Fix Released
Status in linux-azure source package in Jammy:
Fix Released
Status in linux-gcp source package in Jammy:
Fix Released
Status in cloud-init source package in Kinetic:
Invalid
Status in linux source package in Kinetic:
Fix Committed
Status in linux-aws source package in Kinetic:
Fix Committed
Status in linux-azure source package in Kinetic:
Fix Committed
Status in linux-gcp source package in Kinetic:
Fix Committed
Bug description:
Issue
resize2fs utility is used to resize the filesystem and is idempotent
in nature. But in the 5.15 kernel, successive execution of resize2fs
is returning error.
Reproduction step (on AWS):
Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux
5.15.0-1022-aws) in us-west-2 region and attach an EBS volume.
Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p
/mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0
Increase the size of EBS volume.
Run sudo resize2fs /dev/xvdb multiple times.
The first execution returns -
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
old_desc_blocks = 2, new_desc_blocks = 3
The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.
The following execution returns -
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
The filesystem is already 5242880 (4k) blocks long. Nothing to do!
When you run the same step on the latest image ami-0a1d6d351894df6cc
(Linux 5.15.0-1026-aws).
The first execution returns -
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
old_desc_blocks = 2, new_desc_blocks = 3
The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.
The following execution returns
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/xvdb
Couldn't find valid filesystem superblock.
FIX:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
