[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Server nfs-home reports our clientid is in use



Hi folks,

I am running Whezzy on my NFServer and the NFS clients.
Kernel is 

Linux nfs-home.example.com 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt11-1~bpo70+1 (2015-06-08) x86_64 GNU/Linux

Problem: Sometimes a client cannot write to /home 
via NFS anymore. The error message in kern.log on the 
client says

Jul 30 15:53:57 dpcl082 kernel: [2880660.867248] NFS: Server nfs-home reports our clientid is in use
Jul 30 15:53:57 dpcl082 kernel: [2880660.867254] NFS: state manager: lease expired failed on NFSv4 server nfs-home with 
Jul 30 15:54:54 dpcl082 kernel: [2880717.424872] NFS: Server nfs-home reports our clientid is in use
Jul 30 15:54:54 dpcl082 kernel: [2880717.424878] NFS: state manager: lease expired failed on NFSv4 server nfs-home with 
Jul 30 15:55:01 dpcl082 kernel: [2880724.526741] NFS: Server nfs-home reports our clientid is in use
Jul 30 15:55:01 dpcl082 kernel: [2880724.526748] NFS: state manager: lease expired failed on NFSv4 server nfs-home with 
:
:


I have to umount and mount /home to get read access again. 
The kern.log on the server doesn't mention this incident.

Since I saw "NFSv4.1: Fix client id trunking on Linux" 
introduced with 3.16.7-ckt7-1 I wonder if this rings a
bell somewhere?

By now I saw this problem 4 times within the last week. There 
are more than 100 NFS clients, using a static mount of /home ,
i.e. the problem is hard to reproduce.


Every helpful comment is highly appreciated. 


Regards
Harri

Attachment: signature.asc
Description: PGP signature


Reply to: