fstab looks like this: 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
With this setup, /opt and /home are mounted by mountall, however, they are mounted 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) If I remount manually, the clientaddr is correct, so I believe mountall is attempting to mount this too early. Should I report this as a separate bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
