kernel: NFSD: client testing state ID with incorrect client ID

[pharthiphan]

I see couple of clients showing up on the nfs server system messages as "incorrect client ID" and I don't see much on the client system logs.

I have a nfs server running on centos 7 and client's are ubuntu but only these two clients have some clients on nfs server logs

Code: Select all

grep "incorrect client ID" /var/log/messages | awk '{$1=$2=$3=$4=""; print $0}' | sort | uniq -c
   5504     kernel: NFSD: client 10.52.104.56 testing state ID with incorrect client ID
   7966     kernel: NFSD: client 10.52.104.57 testing state ID with incorrect client ID

below outputs from the client node:-

Code: Select all

# mount -t nfs4
home:/home on /home type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.52.104.56,local_lock=none,addr=10.52.96.45)
logs:/tank on /tank type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.52.104.56,local_lock=none,addr=10.52.96.86)

Code: Select all

$ ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.52.104.56  netmask 255.255.240.0  broadcast 10.52.111.255
        inet6 fe80::ae1f:6bff:fe0b:314a  prefixlen 64  scopeid 0x20<link>
        ether ac:1f:6b:0b:31:4a  txqueuelen 1000  (Ethernet)
        RX packets 3082064374  bytes 2759828627966 (2.7 TB)
        RX errors 0  dropped 4  overruns 0  frame 0
        TX packets 2428893676  bytes 1631443236192 (1.6 TB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Code: Select all

ip -s link show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:0b:31:4a brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast   
    2759828770929 3082064983 0       4       0       353430  
    TX: bytes  packets  errors  dropped carrier collsns 
    1631443266340 2428893947 0       0       0       0    

ethtool output from both the clients

Code: Select all

$ ethtool -S eth0 | egrep 'dropped|errors'
     rx_errors: 0
     tx_errors: 0
     rx_dropped: 4
     tx_dropped: 0
     rx_over_errors: 0
     rx_crc_errors: 0
     rx_frame_errors: 0
     rx_fifo_errors: 0
     rx_missed_errors: 0
     tx_aborted_errors: 0
     tx_carrier_errors: 0
     tx_fifo_errors: 0
     tx_heartbeat_errors: 0
     rx_length_errors: 0
     rx_long_length_errors: 0
     rx_short_length_errors: 0
     rx_csum_offload_errors: 0
     rx_fcoe_dropped: 0

Code: Select all

 $ ethtool -S eth0 | egrep 'dropped|errors'
     rx_errors: 0
     tx_errors: 0
     rx_dropped: 9
     tx_dropped: 0
     rx_over_errors: 0
     rx_crc_errors: 0
     rx_frame_errors: 0
     rx_fifo_errors: 0
     rx_missed_errors: 0
     tx_aborted_errors: 0
     tx_carrier_errors: 0
     tx_fifo_errors: 0
     tx_heartbeat_errors: 0
     rx_length_errors: 0
     rx_long_length_errors: 0
     rx_short_length_errors: 0
     rx_csum_offload_errors: 1
     rx_fcoe_dropped: 0

any idea how to investigate this issue ?