Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1023451: Current Bookworm daily image breaks root file system during resize
115 views
Skip to first unread message
Sven Bartscher
Nov 4, 2022, 9:20:05 AM11/4/22
to
Package: cloud.debian.org
Severity: important
I was trying to use the daily image
debian-12-genericcloud-amd64-daily-20221104-1189.qcow2. I booted it in
QEMU as follows:
$ qemu-system-x86_64 -m 1G -device virtio-scsi-pci,id=scsi -device
scsi-hd,drive=hd -drive file=test.qcow2,if=none,id=hd -drive
file=user-data.iso,if=ide,media=cdrom -nographic
When cloud-init gets to the step of resizing the root file system to fit
the disk, it fails with the following error:
[ 160.037486] cloud-init[292]: 2022-11-04 12:56:50,913 -
schema.py[WARNING]: Invalid cloud-config provided: Please run 'sudo
cloud-init schema --system' to see the schema errors.
[ 163.701342] EXT4-fs (sda1): resizing filesystem from 491515 to
4161531 blocks
[ 163.870631] EXT4-fs (sda1): resized filesystem to 4161531
[ 163.914439] EXT4-fs (sda1): Invalid checksum for backup superblock 32768
[ 163.914439]
[ 163.914892] EXT4-fs error (device sda1) in ext4_update_backup_sb:174:
Filesystem failed CRC
[ 163.915287] Aborting journal on device sda1-8.
[ 163.919235] EXT4-fs error (device sda1): ext4_journal_check_start:83:
comm systemd-journal: Detected aborted journal
[ 163.922561] EXT4-fs (sda1): Remounting filesystem read-only
[ 163.922993] EXT4-fs error (device sda1) in ext4_update_backup_sb:174:
Journal has aborted
Many of the following steps fail too, because the root file system is
mounted read-only.
The test.qcow2 above has been created as follows:
qemu-img create -F qcow2 -b
debian-12-genericcloud-amd64-daily-20221104-1189.qcow2 -f qcow2
test.qcow2 16G
The user-data.iso has been created as follows:
genisoimage -output ../user-data.iso -volid cidata -joliet -rock
user-data meta-data
where meta-data is an empty file and user-data has the following contents:
#cloud-config
hostname: test
users:
- name: admin
sudo: ['ALL=(ALL) ALL']
passwd:
$6$CZ6uhDC3EwuDlkLR$tXGFBbAnunjYwT202gdT9idnjE2EAspHn6Dxn7uL7u.WmOUPYa/5D7Bz9XrSnaSpyv7uh.5Mok9bLD/JIhWq21
Regards
Sven
Severity: important
I was trying to use the daily image
debian-12-genericcloud-amd64-daily-20221104-1189.qcow2. I booted it in
QEMU as follows:
$ qemu-system-x86_64 -m 1G -device virtio-scsi-pci,id=scsi -device
scsi-hd,drive=hd -drive file=test.qcow2,if=none,id=hd -drive
file=user-data.iso,if=ide,media=cdrom -nographic
When cloud-init gets to the step of resizing the root file system to fit
the disk, it fails with the following error:
[ 160.037486] cloud-init[292]: 2022-11-04 12:56:50,913 -
schema.py[WARNING]: Invalid cloud-config provided: Please run 'sudo
cloud-init schema --system' to see the schema errors.
[ 163.701342] EXT4-fs (sda1): resizing filesystem from 491515 to
4161531 blocks
[ 163.870631] EXT4-fs (sda1): resized filesystem to 4161531
[ 163.914439] EXT4-fs (sda1): Invalid checksum for backup superblock 32768
[ 163.914439]
[ 163.914892] EXT4-fs error (device sda1) in ext4_update_backup_sb:174:
Filesystem failed CRC
[ 163.915287] Aborting journal on device sda1-8.
[ 163.919235] EXT4-fs error (device sda1): ext4_journal_check_start:83:
comm systemd-journal: Detected aborted journal
[ 163.922561] EXT4-fs (sda1): Remounting filesystem read-only
[ 163.922993] EXT4-fs error (device sda1) in ext4_update_backup_sb:174:
Journal has aborted
Many of the following steps fail too, because the root file system is
mounted read-only.
The test.qcow2 above has been created as follows:
qemu-img create -F qcow2 -b
debian-12-genericcloud-amd64-daily-20221104-1189.qcow2 -f qcow2
test.qcow2 16G
The user-data.iso has been created as follows:
genisoimage -output ../user-data.iso -volid cidata -joliet -rock
user-data meta-data
where meta-data is an empty file and user-data has the following contents:
#cloud-config
hostname: test
users:
- name: admin
sudo: ['ALL=(ALL) ALL']
passwd:
$6$CZ6uhDC3EwuDlkLR$tXGFBbAnunjYwT202gdT9idnjE2EAspHn6Dxn7uL7u.WmOUPYa/5D7Bz9XrSnaSpyv7uh.5Mok9bLD/JIhWq21
Regards
Sven
Bastian Blank
Nov 7, 2022, 2:30:04 PM11/7/22
to
Control: reassign -1 linux/6.0-1~exp1
Control: forcemerge 1023450 -1
On Fri, Nov 04, 2022 at 02:04:05PM +0100, Sven Bartscher wrote:
> [ 163.701342] EXT4-fs (sda1): resizing filesystem from 491515 to 4161531
> blocks
> [ 163.870631] EXT4-fs (sda1): resized filesystem to 4161531
> [ 163.914439] EXT4-fs (sda1): Invalid checksum for backup superblock 32768
> [ 163.914439]
> [ 163.914892] EXT4-fs error (device sda1) in ext4_update_backup_sb:174:
> Filesystem failed CRC
The ext4 maintainer confirmed this is a kernel bug introduced in 6.0.
Bastian
--
Only a fool fights in a burning house.
-- Kank the Klingon, "Day of the Dove", stardate unknown
Control: forcemerge 1023450 -1
On Fri, Nov 04, 2022 at 02:04:05PM +0100, Sven Bartscher wrote:
> [ 163.701342] EXT4-fs (sda1): resizing filesystem from 491515 to 4161531
> blocks
> [ 163.870631] EXT4-fs (sda1): resized filesystem to 4161531
> [ 163.914439] EXT4-fs (sda1): Invalid checksum for backup superblock 32768
> [ 163.914439]
> [ 163.914892] EXT4-fs error (device sda1) in ext4_update_backup_sb:174:
> Filesystem failed CRC
Bastian
--
Only a fool fights in a burning house.
-- Kank the Klingon, "Day of the Dove", stardate unknown
0 new messages