clientid is in use
Subsystems (2)
Occasionally I am seeing the following in our kernel log on a NFS client:
[2321389.137595] NFS: Server enkf reports our clientid is in use [2321389.137615] NFS: state manager: lease expired failed on NFSv4 server enkf with error 1
The result is that the read of the file in question fails. This occurs for multiple kernel versions on multiple machines. Anyone have an idea how I should start debugging this? How is the clientid calculated/assigned?
Signature · 5 lines
Dr. Harry Edmon [email protected], 206-543-0547, FAX: 206-543-0308 Director of IT, College of the Environment and Director of Computing, Dept of Atmospheric Sciences University of Washington, Box 351640, Seattle, WA 98195-1640
Quoted 6 lines · Harry Edmon
Occasionally I am seeing the following in our kernel log on a NFS client:
[2321389.137595] NFS: Server enkf reports our clientid is in use [2321389.137615] NFS: state manager: lease expired failed on NFSv4 server enkf with error 1The result is that the read of the file in question fails. This occurs for multiple kernel versions on multiple machines. Anyone have an idea how I should start debugging this? How is the clientid calculated/assigned?
It depends on the kernel version. You can look in fs/nfs/nfs4proc.c for the nfs4_proc_setclientid function.
Signature · 2 lines
Chuck Lever chuck[dot]lever[at]oracle[dot]com
Quoted 10 lines · Chuck Lever
Quoted 6 lines · Harry Edmon
Occasionally I am seeing the following in our kernel log on a NFS client:
[2321389.137595] NFS: Server enkf reports our clientid is in use [2321389.137615] NFS: state manager: lease expired failed on NFSv4 server enkf with error 1The result is that the read of the file in question fails. This occurs for multiple kernel versions on multiple machines. Anyone have an idea how I should start debugging this? How is the clientid calculated/assigned?
It depends on the kernel version. You can look in
fs/nfs/nfs4proc.cfor thenfs4_proc_setclientidfunction.
I am still occasionally seeing this error. The last time was with the NFS client and server both running kernel 3.11.6. The message was on the client. Here is the mount info from /proc/mounts:
margaret:/home/margaret/margaret /home/disk/margaret nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=140.142.113.26,local_lock=none,addr=128.95.89.30 0 0
I am still looking for ideas on how to debug this.
Signature · 5 lines
Dr. Harry Edmon [email protected], 206-543-0547, FAX: 206-543-0308 Director of IT, College of the Environment and Director of Computing, Dept of Atmospheric Sciences University of Washington, Box 351640, Seattle, WA 98195-1640
Quoted 11 lines · Harry Edmon
Quoted 10 lines · Chuck Lever
Quoted 6 lines · Harry Edmon
Occasionally I am seeing the following in our kernel log on a NFS client:
[2321389.137595] NFS: Server enkf reports our clientid is in use [2321389.137615] NFS: state manager: lease expired failed on NFSv4 server enkf with error 1The result is that the read of the file in question fails. This occurs for multiple kernel versions on multiple machines. Anyone have an idea how I should start debugging this? How is the clientid calculated/assigned?
It depends on the kernel version. You can look in
fs/nfs/nfs4proc.cfor thenfs4_proc_setclientidfunction.
Quoted 7 lines
I am still occasionally seeing this error. The last time was with the NFS client and server both running kernel 3.11.6. The message was on the client. Here is the mount info from
/proc/mounts:margaret:/home/margaret/margaret
/home/disk/margaretnfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=140.142.113.26,local_lock=none,addr=128.95.89.30 0 0I am still looking for ideas on how to debug this.
The server is reporting that your clients are using the same client ID. The client ID is based on the client's hostname. Are your clients dynamically named?
The description of the nfs4_unique_id parameter in linux/Documentation/filesystems/nfs/nfs.txt might be helpful.
Signature · 2 lines
Chuck Lever chuck[dot]lever[at]oracle[dot]com