This bug was fixed in the package mountall - 0.2.5
---------------
mountall (0.2.5) karmic; urgency=low
* Filesystem check progress reporting, including cancellation. LP: 446596.
* When we're waiting for a mountpoint, if a few seconds of inactivity
passes, report what we're waiting for and allow Escape to drop you to
a recovery shell.
* Start usplash for filesystem check progress reporting or when we've
been waiting for more than a few seconds. LP: #431184.
* Hide error removing /forcefsck, people mis-report this as a bug and
don't tell us the error above it.
* Don't call mount.ecryptfs or mount.aufs when adding an entry for
/etc/mtab; these helpers are broken and do not support the -f argument.
This means your passphrase may end up in /etc/mtab, blame them not me.
LP: #431954, #443080.
* Unlink /etc/mtab~ after creating/truncating /etc/mtab and before writing
mtab entries. LP: #431865.
* Stop the recovery shell if the user runs shutdown within it, so we
don't run mountall again. LP: #452196.
* If the root filesystem check fails, we'll need to reboot, so just have
the recovery shell script do that.
* Post-review logic fixes.
-- Scott James Remnant <sc...@ubuntu.com> Tue, 20 Oct 2009 12:19:16
+0100
** Changed in: mountall (Ubuntu Karmic)
Status: Fix Committed => Fix Released
--
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.
Status in “ecryptfs-utils” package in Ubuntu: Triaged
Status in “mountall” package in Ubuntu: Fix Released
Status in ecryptfs-utils in Ubuntu Karmic: Won't Fix
Status in mountall in Ubuntu Karmic: Fix Released
Bug description:
Binary package hint: e2fsprogs
When a check is forced the fsck process seems to hang. This was what was
displayed on screen:
fsck from util-linux-ng 2.16
/dev/sda5 has been mounted 34 times without being checked, check forced
/dev/sda5: 176................. files (2.3% non-contiguous, 48128710/59556......
I left it running four about half an hour but nothing changed and there was no
disk activity the entire time. After a hard reset both sda5 and md0 cleanly
mounted.
This leds me to believe that the boot process will hang on every fsck (as this
happened twice allready, and it hasn't gone successfully yet) and that an
actual check of the filesystem therefore never happens...
Note that sda5 is a normal ext3 filesystem. I also have /dev/md0, but this
wasn't checked when it hanged.
ProblemType: Bug
Architecture: amd64
Date: Mon Oct 5 14:52:19 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: vmnet vmci vmmon nvidia
Package: e2fsprogs 1.41.9-1ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: e2fsprogs
Uname: Linux 2.6.31-11-generic x86_64
_______________________________________________
Mailing list: https://launchpad.net/~ecryptfs
Post to : ecryptfs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ecryptfs
More help : https://help.launchpad.net/ListHelp
