Zhitao Li

Close this issue because it maybe duplicated with [issue](https://github.com/nfs-ganesha/nfs-ganesha/issues/985). It is unclear or not maintained now.

Reopen to wait for confirm from our community :)

There is no description of force-expiring a NFS client according NFS v4.x RFC. And EVENT_RELEASE_IP that forces to expire a client can not work at all according to this [issue](https://github.com/nfs-ganesha/nfs-ganesha/issues/985)....

When a nfs-ganesha node named NodeA crashes, the VIP(virtual IP) will be assigned to another node named NodeB. `EVENT_TAKE_IP` is used to tell the destination NodeB that it will serve...

In our case, lock_state are persisted into FSAL layer. When lock is reclaimed, we check the existence of this lock state from underlying storage. And if it doesn't exist, the...

Our NFS v4.x lock implementation is as follows in general. When lock is acquired, we persist the lock record into FSAL(our backend) with its `clientid4`. We strongly rely on the...

We also change ip_match() implementation (issue https://github.com/nfs-ganesha/nfs-ganesha/issues/985) to match those NFS clients that access the VIP. Should these changes be merged into one patch?

Please review this [patch](https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1193517) on Gerrithub :)

What can I do to move this patch forward?

There maybe something related with https://github.com/nfs-ganesha/nfs-ganesha/issues/1070