bindfs: blocking boot

Bug #430880 reported by Chris Coulson on 2009-09-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)

Bug Description

Binary package hint: mountall

mountall blocks the boot of my machine due to the bindfs mounts i have in my fstab. Unfortunately, I couldn't get much useful debug information from mountall, as my keyboard isn't working that early on in the boot. If I remove the bindfs mount entries, then it boots fine.

Anyway, you might already see the issue if I attach my fstab.

ProblemType: Bug
Architecture: amd64
Date: Wed Sep 16 18:28:50 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: mountall 0.1.5
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SourcePackage: mountall
Uname: Linux 2.6.31-10-generic x86_64

Chris Coulson (chrisccoulson) wrote :
Chris Coulson (chrisccoulson) wrote :

Here is my fstab. These are the 2 entries which cause the issue (if I remove them both, then I can boot ok):

bindfs#/home/.shared /home/shared fuse group=shared-rw,perms=0000:u+rwD:g+rwD:o+rD 0 0
bindfs#/home/.chris+jo /home/chris+jo fuse mirror=@chrisandjo-rw,group=chrisandjo-ro,perms=0000:u+rwD:g+rD 0 0

Once booted, could you put the two mounts back in and then run:

  sudo mountall --debug 2>&1 | tee mountall.log

And attach that log

Changed in mountall (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
tags: added: ubuntu-boot
summary: - mountall blocks boot with bindfs mounts in fstab
+ bindfs: blocking boot
Chris Coulson (chrisccoulson) wrote :
Changed in mountall (Ubuntu):
status: Incomplete → New
Chris Coulson (chrisccoulson) wrote :
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mountall - 0.1.6

mountall (0.1.6) karmic; urgency=low

  [ Scott James Remnant ]
  * Restored mistakenly removed dh_installchangelogs & dh_installdocs.

  * Allow a further udev event for a block-device to retry swapon/mount
    after fsck has been already been completed for a prior event.
  * Massively reduce the pickyness of mountall when it comes to block
    devices; only expect ID_FS_USAGE and ID_FS_TYPE for dm and md devices,
    and don't actually expect the values. For most people this won't make
    a difference, since we use UUID= anyway. But for people with hardcoded
    /dev/sda1 in their fstab, which has multiple metadata, this won't break
    their boot.

  * Only include FHS filesystems in the {virtual,local,remote}-filesystems
    events. This prevents an unmountable entry in fstab blocking things like
    starting D-Bus or the Network which are required to mount that filesystem.
    LP: #430880.
  * Never consider the root filesystem to be virtual or remote, even when
    it is, since we assert that it's already mounted so we don't have to
    take care of it. LP: #431028.
  * Check whether filesystems mounted readonly when we start do not have
    "ro" in their fstab, before assuming we need to remount them.
    Readonly filesystems not in fstab (e.g. LiveCD, Wubi, etc.) never need
    remounting. LP: #431028.
  * Only virtual filesystems will be mounted while the root filesystem is
    readonly, not filesystems such as /usr and /var.
  * fuse filesystems are never considered virtual, since they probably
    need devices, write access and the hand of god to be mounted.

  [ Colin Watson ]
  * Ignore errors from kill in mountall-net, since they're almost certainly
    just because mountall exited before we had a chance to kill it
    LP: #430755.

 -- Scott James Remnant <email address hidden> Wed, 16 Sep 2009 23:55:33 +0100

Changed in mountall (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers