public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: David Teigland <teigland@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: lockd and lock cancellation
Date: Fri, 09 Apr 2010 16:25:09 -0400	[thread overview]
Message-ID: <4BBF8D25.7050506@oracle.com> (raw)
In-Reply-To: <20100409194018.GA11823@redhat.com>

Hi David-

On 04/09/2010 03:40 PM, David Teigland wrote:
> Here's what I think was the first time we discussed cancelation and
> Bruce's provisional locks: http://marc.info/?t=116538335700005&r=1&w=2
> I'm still skeptical of trying to handle cancels, it seems too complex to
> become reliable in the lifetime of nfs3.
>
> What I would be interested to see fixed is this oops that's not difficult
> to trigger by doing lock/unlock loops on a client:
> https://bugzilla.redhat.com/show_bug.cgi?id=502977#c18
>
> But, for all the kernel work on these nfs/gfs/dlm hooks, there's a larger
> issue that no one is working on AFAIK:  the mechanisms for recovering
> client locks on remaining gfs nodes when one gfs node fails.  That would
> take a lot of work, and until it's done all the kernel apis will be a moot
> point since clustered nfs locks on gfs will be unusable.

To support IPv6, I've studied and modified the NFSv2/v3 lock recovery 
mechanisms quite a bit recently.  What kernel APIs do you think would be 
needed to manage cluster lock recovery?  Just something to release stale 
locks on a single node?

-- 
chuck[dot]lever[at]oracle[dot]com

  reply	other threads:[~2010-04-09 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 19:40 lockd and lock cancellation David Teigland
2010-04-09 20:25 ` Chuck Lever [this message]
2010-04-09 20:50   ` David Teigland
  -- strict thread matches above, loose matches on Subject: below --
2010-04-01 12:16 Steven Whitehouse
2010-04-01 12:40 ` Rob Gardner
2010-04-01 13:13   ` Steven Whitehouse
2010-04-01 14:07     ` Rob Gardner
2010-04-01 15:56       ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BBF8D25.7050506@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=teigland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox