[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: qcow2 resize issue with latest unstable cloud images



Hi Bastian and thanks for taking time to test.
I don't think this is related to the image itself.
I just installed debian testing on a physical host, formatting manually
with a 1G / and 3G free behind (installer was based on kernel 6.0 too) .
I booted the machine, then :

---
root@abanc:~# uname -a
Linux abanc 6.0.0-2-powerpc64le #1 SMP Debian 6.0.5-1 (2022-10-28) ppc64le GNU/Linux
root@abanc:~# lsblk
NAME                    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                       8:0    1   3.6T  0 disk
├─sda1                    8:1    1     7M  0 part
├─sda2                    8:2    1 931.3G  0 part /
└─sda3                    8:3    1   976M  0 part [SWAP]
root@abanc:~# growpart /dev/sda 2
CHANGED: partition=2 start=16384 old: size=1953124352 end=1953140735 new: size=7812020224 end=7812036607
root@abanc:~# resize2fs /dev/sda2 950G
resize2fs 1.46.6-rc1 (12-Sep-2022)
Filesystem at /dev/sda2 is mounted on /; on-line resizing required
old_desc_blocks = 117, new_desc_blocks = 119
resize2fs: Read-only file system While checking for on-line resizing support
---

and on the console :

---
[ 5616.327313] EXT4-fs (sda2): Invalid checksum for backup superblock 32768
[ 5616.327313] 
[ 5616.327495] EXT4-fs error (device sda2) in ext4_update_backup_sb:174: Filesystem failed CRC
[ 5616.327518] Aborting journal on device sda2-8.
[ 5616.330649] EXT4-fs error (device sda2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journal
[ 5616.345376] EXT4-fs (sda2): Remounting filesystem read-only
[ 5616.345537] EXT4-fs error (device sda2) in ext4_update_backup_sb:174: Journal has aborted
---

At the moment, this issue has already "migrated" to testing cloud
images.


F.

On Fri, 04 Nov 2022 09:48:35 +0000 Bastian Blank <waldi@debian.org> wrote:
> On Fri, Nov 04, 2022 at 10:14:23AM +0100, Bastian Blank wrote:
> > Maybe running fsck before shipping the image will make it work better.
> > Currently we rely on the kernel of the build system to provide us with a
> > clean file system.
> 
> fsck is not seeing any problem with that filesystem.
> 
> Bastian
> 
> -- 
> I'm a soldier, not a diplomat.  I can only tell the truth.
> 		-- Kirk, "Errand of Mercy", stardate 3198.9


Reply to: