NFS client hang up if storage reply NFS4ERR_DELAY followed by NFS4ERR_SEQ_MISORDERED
Applies to
- ONTAP 9
- NFSv4.1
- pNFS
- RedHat Enterprise Linux (RHEL)
Issue
- After a network partition (network is unavailable for some time) Linux clients can be seen to lose track of NFS4.1 Sequencing
- After the network has recovered, the NFS client has incremented its sequence on the active slot beyond where the server has acknowledged
- This is an indication that multiple sequences have been sent and not retransmitted as the server never receives the missed sequences