"In any case, this isn't an e2fsck bug. The kernel is returning EBUSY;" <-- why couldn't the kernel be returning EBUSY because of an e2fsck bug which attempts to open the device twice (without first closing it)?
Why do I see in the E2fsprogs 1.41.13 (December 13, 2010) release notes: http://e2fsprogs.sourceforge.net/e2fsprogs-release.html http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=blob;f=RELEASE-NOTES 948 Fixed a bug in e2fsck where if both the original and backup superblock 949 are invalid in some way, e2fsck will fail going back to the original 950 superblock because it didn't close the backup superblock first, and 951 the exclusive open prevented the file system from being reopened. Notice I am having this problem on version 1.42 so either this isn't the same issue as fixed in 1.41.13, the fix didn't work, or it somehow isn't in 1.42. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711799 Title: e2fsprogs wrongly identifies ext4 as mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/711799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
