Control: forwarded -1 https://github.com/tytso/e2fsprogs/pull/118
On Wed, Feb 01, 2023 at 06:07:25PM +0100, Gioele Barabucci wrote: > debvm-create converts the ext2 filesystem created by mmdebstrap to ext4 > using the following tune2fs command: > > tune2fs ... -O extents,uninit_bg,dir_index,has_journal "$IMAGE" > > The ext4 filesystem created in this way does not have some of the features > that a filesystem created with mkfs.ext4 would have: > > $ truncate -s "1GiB" e2 > $ /sbin/mkfs.ext2 e2 > $ /sbin/tune2fs -O extents,uninit_bg,dir_index,has_journal e2 > > $ truncate -s "1GiB" e4 > $ /sbin/mkfs.ext4 e4 > > $ diff -U7 <(/sbin/dumpe2fs ./e2 | grep -m1 feat | tr ' ' '\n') > <(/sbin/dumpe2fs ./e4 | grep -m1 feat | tr ' ' '\n') > > has_journal > ext_attr > resize_inode > dir_index > filetype > extent > +64bit > +flex_bg > sparse_super > large_file > -uninit_bg > +huge_file > +dir_nlink > +extra_isize > +metadata_csum > > My (debatable) expectation is that the ext4 filesystem would have at least > all features of a standard ext4 filesystem. This kinda is right. We could slightly improve this, but in the end we want to replace genext2fs with mkfs.ext4 and that depends on it supporting tarball input. So do you think we should mess with the tune2fs invocation in the interim or is it good enough for now? Helmut
