NLM reclaim without Ganesha loosing the locks
Hello All, For one case in our cluster, I need to send sm-notify to the client even when Ganesha has not restarted, but it is in Grace period. So the client sends reclaim to a server which has not actually lost the locks. Can Ganesha handle NLM reclaim locks without actually loosing the locks first? Thanks & Regards, Suhrud
I believe this should be fine. Daniel On 12/28/2018 01:51 AM, Suhrud Patankar wrote:
Hello All,
For one case in our cluster, I need to send sm-notify to the client even when Ganesha has not restarted, but it is in Grace period. So the client sends reclaim to a server which has not actually lost the locks.
Can Ganesha handle NLM reclaim locks without actually loosing the locks first?
Thanks & Regards, Suhrud _______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
sm-notify has a state number, hopefully that should help the client not reclaim the locks. Regards, Malahal. On Mon, Jan 7, 2019 at 7:51 PM Daniel Gryniewicz <dang@redhat.com> wrote:
I believe this should be fine.
Daniel
On 12/28/2018 01:51 AM, Suhrud Patankar wrote:
Hello All,
For one case in our cluster, I need to send sm-notify to the client even when Ganesha has not restarted, but it is in Grace period. So the client sends reclaim to a server which has not actually lost the locks.
Can Ganesha handle NLM reclaim locks without actually loosing the locks first?
Thanks & Regards, Suhrud _______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
_______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
On Mon, Jan 7, 2019 at 8:28 PM Malahal Naineni <malahal@gmail.com> wrote:
sm-notify has a state number, hopefully that should help the client not reclaim the locks.
In my case, I need to increase the state number for sm-notify (even without Ganesha restart). This makes the client to reclaim. The issue I see is, during reclaims client always uses the state number as zero. So, if client had taken lock with state number 5 and then it reclaims it, it reclaims with state number 0. This adds two entries at Ganesha side, one for each state number. This works in Ganesha restart case. As I am getting the reclaims without Ganesha restart, there are two entries on server side. This cause the issue - even after client unlocks the lock, the file remains locked on the server side. Thanks & Regards, Suhrud
Regards, Malahal.
On Mon, Jan 7, 2019 at 7:51 PM Daniel Gryniewicz <dang@redhat.com> wrote:
I believe this should be fine.
Daniel
On 12/28/2018 01:51 AM, Suhrud Patankar wrote:
Hello All,
For one case in our cluster, I need to send sm-notify to the client even when Ganesha has not restarted, but it is in Grace period. So the client sends reclaim to a server which has not actually lost the locks.
Can Ganesha handle NLM reclaim locks without actually loosing the locks first?
Thanks & Regards, Suhrud _______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
_______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
_______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
Hmm if reclaims come in with state number 0 that may cause problems with handling client restart. I need to think about this. We should know however that clients will reclaim locks we didn’t lose. We could just ignore the reclaims. Frank Sent from my iPhone
On Jan 7, 2019, at 9:27 PM, Suhrud Patankar <suhrudpatankar@gmail.com> wrote:
On Mon, Jan 7, 2019 at 8:28 PM Malahal Naineni <malahal@gmail.com> wrote:
sm-notify has a state number, hopefully that should help the client not reclaim the locks.
In my case, I need to increase the state number for sm-notify (even without Ganesha restart). This makes the client to reclaim.
The issue I see is, during reclaims client always uses the state number as zero. So, if client had taken lock with state number 5 and then it reclaims it, it reclaims with state number 0.
This adds two entries at Ganesha side, one for each state number. This works in Ganesha restart case. As I am getting the reclaims without Ganesha restart, there are two entries on server side.
This cause the issue - even after client unlocks the lock, the file remains locked on the server side.
Thanks & Regards, Suhrud
Regards, Malahal.
On Mon, Jan 7, 2019 at 7:51 PM Daniel Gryniewicz <dang@redhat.com> wrote:
I believe this should be fine.
Daniel
On 12/28/2018 01:51 AM, Suhrud Patankar wrote: Hello All,
For one case in our cluster, I need to send sm-notify to the client even when Ganesha has not restarted, but it is in Grace period. So the client sends reclaim to a server which has not actually lost the locks.
Can Ganesha handle NLM reclaim locks without actually loosing the locks first?
Thanks & Regards, Suhrud _______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
_______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
participants (4)
-
Daniel Gryniewicz -
Frank Filz -
Malahal Naineni -
Suhrud Patankar