[Kernel-packages] [Bug 1368922] Re: nfsd stops running shortly after clients connect
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- 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: Expired 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1368922] Re: nfsd stops running shortly after clients connect
we downgraded kernel from : GNU/Linux 3.2.0-67-generic x86_64 to GNU/Linux 3.2.0-61-generic x86_64 and we no longer have this issue . -- 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: Incomplete 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1368922] Re: nfsd stops running shortly after clients connect
** Tags added: needs-bisect -- 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: Incomplete 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1368922] Re: nfsd stops running shortly after clients connect
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc5-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: kernel-da-key trusty -- 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: Incomplete 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1368922] Re: nfsd stops running shortly after clients connect
Unable to run apport-collect on this server. Bug is very reliably reproduced, however. I have replicated it on test boxes I set up (to try to rule out possibility of hardware on the server). ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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. 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1368922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1368922] Re: nfsd stops running shortly after clients connect
** 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
