So, NFS4ERR_OLD_STATEID can only happen in one circumstance: when the
State presented by the client doesn't match the State that Ganesha
expects. In this case, it's the sequence number that's off-by-one.
This could be the result of a replay, but the code checks for this, and
the owners must
Hi All,
As reported by customer, NFSv4 client, if left open the session overnight,
gets nothing for command "pwd". Customer is rebooting the client to
overcome this issue in the next morning.
Is this expected to happen ? If not is it related to any configuration
setting ? Ganesha bug / Client bug
