This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.
Jeff revamped Grace about a year ago as part of his work on clustered
FSAL_CEPH. This may have fixed the issue.
Looking through, the only code that doesn't directly check the grace
state is the NFS4_OP_OPEN code. If the client sends a CLAIM_NULL but
has not finished it's reclaim, then we'll return NFS4ERR_GRACE. My
quick scan doesn't show us doing anything with that field when Grace
expires, so it's possible it hangs around...
Daniel
On 8/10/19 12:32 PM, Sriram Patil via Nfs-ganesha-devel wrote:
This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.
Hi,
Was this fixed in some changes later? I have seen this a couple of times
in some of our test runs.
I have seen NFS4ERR_GRACE on open even when there are no NFS server
restarts.
Thanks,
Sriram
------------------------------------------------------------------------
*From:* Frank Filz <ffilz...@mindspring.com>
*Sent:* Friday, March 16, 2018 5:30 AM
*To:* 'NFS Ganesha Developers' <nfs-ganesha-devel@lists.sourceforge.net>
*Subject:* [Nfs-ganesha-devel] DSESS9002 and DSESS9003 test cases result
in NFS4ERR_GRACE
Does anyone know why an open well after Ganesha comes up is returning
NFS4ERR_GRACE?
I think it has something to do with the cid_reclaim_complete in the NFS
v4.1 clientid.
Thanks
Frank
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
