Public bug reported: With the following fstab:
proc /proc proc nodev,noexec,nosuid 0 0 /dev/mapper/vg0-fat_client / ext4 relatime,errors=remount-ro 0 1 /dev/mapper/vg0-swap none swap sw 0 0 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/nfs/rpc_pipefs type rpc_pipefs (rw) spitzer:/home on /home type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2) spitzer:/opt on /opt type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2) Since this happens on all clients (they all get same clientaddr), this results in a frozen mount (cf http://thread.gmane.org/gmane.linux.nfs/47780) 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 ProcVersionSignature: Ubuntu 3.0.0-23.39~lucid1-server 3.0.36 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 ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037192 Title: NFS shares are mounted with wrong clientaddr or not at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
