NFS shares are mounted with wrong clientaddr or not at all
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
With the following fstab:
proc /proc proc nodev,noexec,nosuid 0 0
/dev/mapper/
/dev/mapper/
spitzer:/opt /opt nfs4 auto 0 0
spitzer:/home /home nfs4 auto 0 0
The /opt and /home are sometimes not mounted at all, and sometimes with the wrong clientaddr:
$ mount | grep nfs
rpc_pipefs on /var/lib/
spitzer:/home on /home type nfs4 (rw,clientaddr=
spitzer:/opt on /opt type nfs4 (rw,clientaddr=
Since this happens on all clients (they all get same clientaddr), this results in a frozen mount (cf http://
The "spitzer" host is only reachable via a tinc VPN, and mounting (or remounting) manually after boot always works and results in the correct clientaddr, so I believe that mountall is attempting to mount this too early.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mountall 2.15.3
ProcVersionSign
Uname: Linux 3.0.0-23-server x86_64
Architecture: amd64
Date: Wed Aug 15 12:16:17 2012
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mountall
Thanks for the report. Can you please capture some debugging output from mountall so we can see what's happening? The most straightforward way to do this is to modify /etc/init/ mountall. conf and replace this line:
exec mountall --daemon $force_fsck $fsck_fix
with this:
exec mountall --daemon --verbose $force_fsck $fsck_fix > /dev/mountall.log 2>&1
Be aware of course that any typos in this job file may render your system unbootable and require recovery by way of rescue mode and/or editing from the initramfs.