Package: e2fsprogs Version: 1.44.5-1 Severity: normal Tags: lfs Dear Maintainer,
I created a rootfs containing a file with a size greater than 5G. I used mkfs to apply the rootfs on an image. If I applied the Image the file had changed (verified with md5sum). This bug is fixed upstream[1] with version 1.44.6. The fixing commit is 1eec7413677ee15182470928c7236969d32d8426. [1] git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git Steps to reproduce: mkdir rootfs dd if=/dev/urandom of=rootfs/bigfile bs=4M count=1280 dd if=/dev/zero of=image bs=4M count=2000 mkfs.ext4 image -d rootfs mount -o loop,ro image /mnt md5sum rootfs/bigfile /mnt/bigfile Kind regards Quirin -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages e2fsprogs depends on: ii libblkid1 2.33.1-0.1 ii libc6 2.28-10 ii libcom-err2 1.44.5-1 ii libext2fs2 1.44.5-1 ii libss2 1.44.5-1 ii libuuid1 2.33.1-0.1 Versions of packages e2fsprogs recommends: pn e2fsprogs-l10n <none> Versions of packages e2fsprogs suggests: pn e2fsck-static <none> pn fuse2fs <none> pn gpart <none> ii parted 3.2-25 -- no debconf information
