kernel-packages team mailing list archive

[Mip Mipendorf <1368922@xxxxxxxxxxxxxxxxxx>]

** Description changed:

- Ubuntu 14.04.1 server fully updated. nfs-kernel-server stops working.
- Sudo service nfs-kernel-server restart will appear to work, bu t sudo
- service nfs-kernel-server status will show nfsd not running. It can't be
- restarted successfully unless rebooted. nfsd will stay up until client
- mount and use the share. dmesg showed tainted kernel. The only way to
- stop this behavior was to edit /etc/default/nfs-kernel-server
- RPCMOUNTDOPTS="--manage-gids --no-nfs-version 4" and edit  fstab on the
- clients to use vers=3 as a mount option.
+ Ubuntu 14.04.1 server fully updated. nfs-kernel-server stops working,
+ hanging clients who have mounted shares. Sudo service nfs-kernel-server
+ restart will appear to work, but sudo service nfs-kernel-server status
+ will show nfsd not running. It can't be restarted successfully unless
+ rebooted. nfsd will stay up until clients mount and use the share. dmesg
+ shows tainted kernel. The only way to stop this behavior was to edit
+ /etc/default/nfs-kernel-server RPCMOUNTDOPTS="--manage-gids --no-nfs-
+ version 4" and edit  fstab on the clients to use vers=3 as a mount
+ option.
+ 
+ Testing now to see whether all that's required to trigger nfs-kernel-
+ server crash is a client w/out vers=3 mount option.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1368922

Title:
  nfsd stops running shortly after clients connect

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.1 server fully updated. nfs-kernel-server stops working,
  hanging clients who have mounted shares. Sudo service nfs-kernel-
  server restart will appear to work, but sudo service nfs-kernel-server
  status will show nfsd not running. It can't be restarted successfully
  unless rebooted. nfsd will stay up until clients mount and use the
  share. dmesg shows tainted kernel. The only way to stop this behavior
  was to edit /etc/default/nfs-kernel-server RPCMOUNTDOPTS="--manage-
  gids --no-nfs-version 4" and edit  fstab on the clients to use vers=3
  as a mount option.

  Testing now to see whether all that's required to trigger nfs-kernel-
  server crash is a client w/out vers=3 mount option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1368922/+subscriptions