NFS4ERR_EXPIRED errors due to incorrect 'clientaddr' NFS mount option
Issue
An NFSv4 share becomes inaccessible to some of the NFS clients accessing it.
On the affected systems, processes accessing it are in 'D' state. In dmesg we can see messages like this:
NFS: state manager: reclaim nograce failed on NFSv4 server xx.x.x.xx with error 10011
NFS: state manager: reclaim nograce failed on NFSv4 server xx.x.x.xx with error 10011
NFS: state manager: reclaim nograce failed on NFSv4 server xx.x.x.xx with error 10011
Error Code 10011 is NFS4ERR_EXPIRED .
The NFS Server is accessible (network is working) from the affected systems and we can navigate to exported directory inside the server.
Environment
RHEL 6 or RHEL 7 NFSv4 clients accessing the same NFS Share using 'clientaddr' mount option.
Server exports:
$ more exports
/myshare <client1_ip_addr>(rw,sync,all_squash,anonuid=XXXX,anongid=XXXX)
/myshare <client2_ip_addr>(rw,sync,all_squash,anonuid=XXXX,anongid=XXXX)
NFS clients:
<server_ip_addr>:/myshare /myshare nfs rw,nfsvers=4,addr=<server_ip_addr>,clientaddr=<client_ip_addr>
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
