NFSv4 owner sequence ID is not properly compared
Applies to
- ONTAP 9
- Cluster Data ONTAP 8
- Data ONTAP 7-mode
- NFSv4.1
Issue
In a trace we see that the storage responds with the NFS4ERR_BAD_SEQID
error from the very first time the client initiated a request with a Sequence ID higher than: 0x0fffffff (7f)
. In other words, when the Sequence ID sent from the client uses the last bit.
Example from a client trace with the issue: