Ubuntu
mountall package

boot stops due to failed mounting of a sshfs partition

Bug #507613 reported by Benjamin Drung
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: mountall

I have following partition in my /etc/fstab:
sshfs#skipper@deep-thought:/home/skipper/archive /home/skipper/archive fuse allow_other,ro 0 0

The boot process stops after mountall failed to mount this partition. I expect the system to continue booting and retrying to mount this partition until the network connection is up (like it worked a week ago).

mountall: mount /home/skipper/archive [789] terminated with status 1
mountall: Filesystem could not be mounted: /home/skipper/archive

ProblemType: Bug
Architecture: amd64
Date: Thu Jan 14 20:23:52 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: mountall 2.4
ProcEnviron:
 LANGUAGE=de_DE.UTF-8
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SourcePackage: mountall
Tags: lucid
Uname: Linux 2.6.32-10-generic x86_64

Revision history for this message
Benjamin Drung (bdrung) wrote :
Revision history for this message
Benjamin Drung (bdrung) wrote :

Here is an screenshot of kvm attached.

Revision history for this message
Nikolaus Rath (nikratio) wrote :

So nothing at all happens after that message? That sounds similar to bug #485709

Revision history for this message
Benjamin Drung (bdrung) wrote :

Yes, nothing happens after that message. It's probably related to bug #485709.

Revision history for this message
Nikolaus Rath (nikratio) wrote :

I guess in that case Scott will be interested in the mountall --debug output for your system as well.

Revision history for this message
Benjamin Drung (bdrung) wrote :

How do I run mountall with --debug? Which file do I have to edit for it?

Revision history for this message
Nikolaus Rath (nikratio) wrote :

Take a look at bug #485709. You have to edit /etc/init/mountall.conf and probably need to redirect the output somewhere.

Revision history for this message
Benjamin Drung (bdrung) wrote :

Just for my memory: I created a new small partition /dev/vda3 and applied the attached patch to /etc/init/mountall.conf.

Revision history for this message
Benjamin Drung (bdrung) wrote :

Attached is the log file. The system was updated to lucid beta 1 and mountall is at version 2.8 now.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

This will now prompt for you, asking whether you'd like to continue or drop to a shell

Changed in mountall (Ubuntu):
status: New → Fix Released
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Err, sorry, I appear to have confused two bugs - this is a network mount so should be retried

Changed in mountall (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

If you change the fstab line to:

sshfs#skipper@deep-thought:/home/skipper/archive /home/skipper/archive fuse allow_other,ro,_netdev 0 0

does it work?

Revision history for this message
Benjamin Drung (bdrung) wrote :

Yes, with _netdev it works like it should.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Ok, according to the mount manpage, that's necessary for mount to *know* it's a network device (since it's fuse)

Changed in mountall (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
elineis - Pierre-Mael Cretinon (elineis.pmc) wrote :

May also be related to bug 571444 (https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/571444) ...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.