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 req...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:
The storePool resources are specifically for doing NFSv4/4.1 state work, they do not keep track of open/locked files at the file system layer (dblade). Exhaustion of the storePool occurs at the Networ...The storePool resources are specifically for doing NFSv4/4.1 state work, they do not keep track of open/locked files at the file system layer (dblade). Exhaustion of the storePool occurs at the Network layer (nblade) of the node where the LIF is mounted. In this case, the server will not remove the OpenState object and the resource is never returned to the pool. These allocations are on the "networking" layer (nblade) of ONTAP which is the node that is being used for connections.