ecryptfs team mailing list archive

[Scott James Remnant <scott@xxxxxxxxxxxxx>]

Dustin: in the mount manpage:

       -f     Causes everything to be done except for the actual system  call;
              if  it's  not  obvious, this ``fakes'' mounting the file system.
              This option is useful in conjunction with the -v flag to  deter‐
              mine what the mount command is trying to do. It can also be used
              to add entries for devices that were mounted earlier with the -n
              option.  The  -f  option checks for existing record in /etc/mtab
              and fails when the record already exists (with regular  non-fake
              mount, this check is done by kernel).

It's one of the standard options that util-linux-ng will always pass to
its helper.  Others include -s, -n, -v and -o

If this is hard to add to ecryptfs, I can ensure mount never calls
mount.ecryptfs

** Also affects: mountall (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: mountall (Ubuntu Karmic)
       Status: New => Fix Committed

** Changed in: mountall (Ubuntu Karmic)
   Importance: Undecided => Medium

** Changed in: mountall (Ubuntu Karmic)
     Assignee: (unassigned) => Scott James Remnant (scott)

-- 
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: Incomplete
Status in “mountall” package in Ubuntu: Fix Committed
Status in ecryptfs-utils in Ubuntu Karmic: Incomplete
Status in mountall in Ubuntu Karmic: Fix Committed

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