nfs-utils: nfsserver restart should kill and recreate nfsd kernel threads
authorQiang Chen <qiang.chen@windriver.com>
Fri, 25 Oct 2013 06:49:11 +0000 (14:49 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sat, 26 Oct 2013 15:08:40 +0000 (16:08 +0100)
commit50f7d27426a25c10b293964bdb1ba915b6de8a5b
treec9c483812c78155fa019b66915cc155c931a1d34
parent105af7486091a88e4d5c1e83bf0a00106834805a
nfs-utils: nfsserver restart should kill and recreate nfsd kernel threads

nfsserver restart without killing kernel threads worked when portmap
was the rpc publishing process and portmap was restarted.
When rpcbind replaces portmap, nfsserver restart in this way does not
work after an rpcbind restart.

Steps to reproduce:
1). Make ext3 filesystem image on local host.
cd /root
dd if=/dev/zero of=test bs=1024K count=50
mkfs.ext3 -F test

2). runqemu qemux86-64
mkdir /mnt/wrtest
mount -t ext3 -o loop test /mnt/wrtest
echo "/mnt/wrtest *(sync,rw,no_subtree_check,no_root_squash)" > /etc/exports
/etc/init.d/rpcbind restart
/etc/init.d/nfsserver restart
showmount -e localhost
mkdir wrtest
mount -t nfs localhost:/mnt/wrtest wrtest

mount: mounting localhost:/mnt/wrtest on wrtest failed: Connection refused

Modifying the nfsserver script to kill and restart kernel threads on
restart makes the problem go away and is consistent with current
RHEL/SUSE and Ubuntu/Debian mechanisms of handling the nfs server.

(From OE-Core rev: 1a96b8d7dfc490fc61bbd470a8b09065750cd563)

Signed-off-by: Rich Dubielzig <rich.dubielzig@windriver.com>
Signed-off-by: Qiang Chen <qiang.chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-connectivity/nfs-utils/nfs-utils/nfsserver