© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Thanks for the response Theodore.
Yes it was definitely not mounted. I checked /proc/mounts (grep sda1 /proc/mounts), the mount -l command itself and also issued several umount /dev/sda1 to be sure. (I do have 10 years of Linux experience.)
The output from e2fsck /dev/sda1 was the same as others are having:
e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Device or resource busy while trying to open /dev/sda1
Filesystem mounted or opened exclusively by another program?
Also got this on the SystemRescueCD:
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext4: Device or resource busy while trying to open /dev/sda1
Filesystem mounted or opened exclusively by another program?
I did a "equery list|grep e2fsprog" on the systemrescueCD to confirm it is ver 1.41.14. Maybe Gentoo has missed your upstream patch for this bug??
I ended up using Slax 6.1.2 with e2fsprogs 1.41.3 to fix the partition and allow the Ubuntu 10.10 system to boot normally. I couldn't delay to do any further testing as it was a laptop of a university Lecturer that had to prepare classes for this week coming (emergency situation).
So maybe I found a new, slightly different bug?
How can one purposely corrupted a FS/journal for testing?