This bug was fixed in the package e2fsprogs - 1.41.14-1ubuntu1 --------------- e2fsprogs (1.41.14-1ubuntu1) natty; urgency=low * Merge from debian experimental (LP: #681418), remaining changes: - debian/control: Do not build-depend on dietlibc-dev, which is universe. - debian/rules: + Do now allow pkg-create-dbgsym to operate on this package. + Build with -O2 on powerpc to avoid a suspected toolchain bug. - debian/e2fsprogs.preinst: Do not include /etc/e2fsck.conf and remove on upgrade. e2fsprogs (1.41.14-1) experimental; urgency=low * New upstream release * Fixed a FTBFS on big-endian architectures * Fixed spurious warning in mke2fs * resize2fs now works correctly on devices exactly 16TB * resize2fs will no longer clear the resize_inode feature when the number of reserved GDT blocks reaches 0. This allows a file system with the flex_bg feature to be subsequently shrunk. * e2fsck will no longer use the extended rec_len encoding for file systems whose blocksize is less than 64k, to catch fs inconsistencies which the kernel will complain about. e2fsprogs (1.41.13-1) unstable; urgency=low * New upstream release * E2fsck can now do journal-only replays via "e2fsck -E journal_only" * E2fsck now understands UUID= and LABEL= specifiers for the -j option (Closes: #559315) * E2fsck.conf now supports a new config option, which forces the problem not to be fixed: problems/