Fixed in 2013.
** Changed in: e2fsprogs (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1186331
Title:
[PATCH] e2fsck hangs up boot process because "Device or resource busy
while checking ext3 journal for foobar"
Status in e2fsprogs package in Ubuntu:
Fix Committed
Bug description:
I installed Kubuntu 13.04 x64 on a new SSD, but pointed its ext4
journal to another partition on a spinning disk (same block size, of
course).
At every boot, e2fsck prompts me to check / for errors but it dies
because:
fsck.ext4: Device or resource busy while checking ext3 journal for
foobar
foobar: ********** WARNING: Filesystem still has errors **********
[Please, also note: If I press I to ignore and continue the boot
process, it complains about /tmp not being ready yet (I used bind in
fstab because it's on another partition). So I press S to skip the
mount and access lightdm which can't login yet because /tmp is
unmounted (it would just restart itself). Accessing the tty with
CTRL+ALT+F1 works and I can "sudo mountall" to correctly mount /tmp,
then login and use the system as usual.]
Using a LiveCD to fsck the / partition shows that the filesystem is
clean.
I built e2fsck from source and applied this patch
http://www.spinics.net/lists/linux-ext4/msg38096.html before compiling
and it solved the problem.
Now the boot-up process is smooth and it also carried away the /tmp
not ready issue.
Please, apply this patch to e2fsprogs.
If you need more info, please just tell me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1186331/+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
