Sorry, the same behavior. But i found something else... It is very frustrating, to be apparent the only one having this problem, so i try to setup a nfsv4 server on Ubuntu (14.04.5 with linux-generic-lts-wily kernel 4.2.0-42)
/etc/exports: /home/exports *(rw,fsid=0,crossmnt,no_subtree_check,sync) /home/exports/user *(rw,nohide,insecure,no_subtree_check,sync) /home/exports/staff *(rw,nohide,insecure,no_subtree_check,sync) Client (Ubuntu 16.04.1) /etc/fstab server:/user /home/server/user nfs _netdev,auto,rw,noatime,nfsvers=4,sync 0 0 server:/staff /home/server/staff nfs _netdev,auto,rw,noatime,nfsvers=4,sync 0 0 mount -a or command line mount works without problem ... --- The behavior is not exactly the same as in our enviorment with a FreeBSD Server but similar i think. Default installation kernel 4.4.0-31-generic : Ok, boot without problem Latest kernel from repo 4.4.0-59 and all other kernel i tested, inclusive the latest mainline kernel 4.9.4 a. Booting with only one auto entry in /etc/fstab : No problem b. Booting with both auto entries in /etc/fstab : The first share will mount fast. The boot log show : "A start job is running for /home/server/staff (1min 14s / 1min 38s)" After timeout is expired the computer finished booting but without mounting the second share. After logging i can mount the second share without problems So the kernel do not crash with a ubuntu nfs server ... bit maybe the main reason for the problem is the same ?! --- Is there anyone could confirm this behavior in his environment ? So that i do not feel so alone any longer ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650336 Title: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs