It depends on the version of e2fsprogs in Ubuntu (which is't specified in this bug report).
The bug appeared in 1.42.9-3, and was fixed in 1.42.11-1. The bigalloc file system is also notone which is used by default by most users. (and probably shouldn't be unless you really know what you are doing; there are real tradeoffs involved with its use, so it's a bit of an advanced feature). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1365864 Title: fsck.ext4 broken on FS created with "bigalloc" Status in “e2fsprogs” package in Ubuntu: New Bug description: Main reference: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=744953 e2fsprogs in Ubuntu 14.04 is affected by this bug that, " caused e2fsck to abort a journal replay on a filesystem with bigalloc enabled." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
