linux-ext4 - packed_meta_blocks=1 incompatible with resize2fs?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <49752bf2-71ec-7fbf-dcdf-93940cfa92c9@robertoragusa.it>
Date:   Mon, 26 Jun 2023 11:15:14 +0200
From:   Roberto Ragusa <mail@...ertoragusa.it>
To:     "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: packed_meta_blocks=1 incompatible with resize2fs?

Hi,

by using

mkfs.ext4 -E packed_meta_blocks=1

all the fs metadata is placed at the start of the disk.
Unfortunately I have not found a way to enlarge the fs
and maintain this property, new metadata is allocated from the
added space.

My attempts to work around the issue have failed:
- adding resize=4290772992 in mkfs doesn't help
- creating a bigger fs with packed_meta_blocks, then shrinking it,
then re-extending it to the original size still allocates from the
new space

Is there a way to have metadata at the beginning of the disk
and be able to enlarge the fs later?
Planning to do this on big filesystems, placing the initial part
on SSD extents; reformat+copy is not an option.

This mailing list appears the best place to ask, sorry if this is
considered off topic.
Thanks.

-- 
    Roberto Ragusa    mail at robertoragusa.it