liyinshubyte
liyinshubyte
@ffilz Hi, there is another crash case, suppose open_state's ref count is 1: thread1: [nfs4_op_close.c:180](https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/Protocols/NFS/nfs4_op_close.c#L180) inc open_state's ref to 2 thread2: [nfs4_op_lock.c:178](https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/Protocols/NFS/nfs4_op_lock.c#L178) inc open_state's ref to 3 thread1: [nfs4_op_close.c:306](https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/Protocols/NFS/nfs4_op_close.c#L306) dec...
@ffilz Thanks the reply, we plan to support state persistence. Is there any discussion before ? so that we can consider more.
@ffilz Thanks the reply, we will first work on NFSv4.1+, and first support lock persistence.
@ffilz Thanks the reply. If we first support lock persistence, is it much easier ?
> The "theory" is laid out in this slide deck (for the most part): > > > [http://nfsv4bat.org/Documents/BakeAThon/2018/Active_Active%20NFS%20Server...](http://nfsv4bat.org/Documents/BakeAThon/2018/Active_Active%20NFS%20Server%20Recovery.pdf) > > Otherwise, when the Ganesha process fails (whether the process itself...
@ffilz Thanks the reply, I have another question, sorry for that. I use NFSv3 in ganesha, for example ganesha's ip is 1.1.1.1, and in front of ganesha we have a...
@ffilz Thanks the reply, I have another question, sorry for that. How can I make client reclaim lock when create session, even without ganesha restart ? We need this in...
> Possibly you could even persist the union of the access modes and deny modes to allow non-conflicting opens to occur. @ffilz As the NFSv4 proto describes, only windows have...
> If possible, I suggest you try and join our community calls at 7:00 AM Pacific Time on Tuesdays. I think your needs are in much alignment with Googles. @ffilz...
> So possibly with enough information, we could use NFS4ERR_STALE_STATEID or NFS4ERR_STALE_CLIENTID to trigger the client, but we need to persist enough information to validate the stateid or clientid. And...