On Oct 31, 2013, at 5:22 PM, Harry Edmon <harry@xxxxxx> wrote: > On 08/04/13 12:20, Chuck Lever wrote: >> On Aug 2, 2013, at 12:15 PM, Harry Edmon <harry@xxxxxx> wrote: >> >>> 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? >> It depends on the kernel version. You can look in fs/nfs/nfs4proc.c for the nfs4_proc_setclientid function. >> > 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. 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. -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
