Unable to mount nfs file systems on boot on diskless client

Bug #104961 reported by Regnar Bang Lyngsø
This bug report is a duplicate of:  Bug #46516: NFSv4 mounts often missing after boot. Edit Remove
2
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

just made a diskless client with Ubuntu 6.10 Edgy Eft.

The root nfs file system works fine.

Other NFS file systems, however, are not mounted during boot.

Line in /etc/fstab

askepot:/home /home nfs auto,rw,user,hard,intr,exec 0 0

I am using a fully updated system.

Found out that others are experiencing the same problem with Feisty:

http://ubuntuforums.org/showthread.php?p=2308087

I have nailed it down to the following line in /etc/init.d/mountall.sh:

mount -a -t noproc,nfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs

Running this in a terminal (with sudo) also results in failing nfs mount.

However, if the noproc is removed - or moved after the nfs part - nfs mount is mounted correctly.

e.g,
sudo mount -a -t nfs,noproc,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs

works fine - same goes for

sudo mount -a -t nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs,nfs,noproc

and even

sudo mount -a -t smbfs,noproc,nfs,nfs4,cifs,ncp,ncpfs,coda,ocfs2,gfs

works. It seems to fail only if noproc is the first type written in the list.

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

Other bug subscribers

Remote bug watches

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