This sounds like a different problem, right? You've already blown away the original contents of the disk, so it's going to be impossible for us to try to reproduce what was going on on the Ubuntu e2fpsrogs version 1.40.8.
As for the "device or resource is busy", that means something else has the device open for exclusive access; maybe another e2fsck process, or the filesystem is mounted, etc. That's a totally separate issue, and it's a safegaurd to protect against users who accidentally try to run fsck on a filesystem which is mounted by /etc/mtab is corrupted, or who had forgotten that they or someone else was running e2fsck in another window, etc. -- e2fsck crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/257048 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
