From: Wendy Cheng <s.wendy.cheng@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfs@lists.sourceforge.net,
Erik Hensema / HostingXS Internet Services
<hensema-yolSOB3tinz/D1n+0JDH9g@public.gmane.org>
Subject: Re: [NFS] Forcefully resetting a lock
Date: Fri, 18 Apr 2008 09:02:06 -0500 [thread overview]
Message-ID: <4808A9DE.9040304@gmail.com> (raw)
In-Reply-To: <20080417215222.GK9912@fieldses.org>
J. Bruce Fields wrote:
> On Wed, Apr 16, 2008 at 02:39:19PM -0500, Wendy Cheng wrote:
>
>> J. Bruce Fields wrote:
>>
>>> On Wed, Apr 16, 2008 at 10:15:19AM -0500, Wendy Cheng wrote:
>>>
>>>
>>>> Erik Hensema / HostingXS Internet Services wrote:
>>>>
>>>>
>>>>> Hi all,
>>>>>
>>>>> Sometimes a file lock gets stuck. Is there any way on either server
>>>>> or client to obtain a list of locks? Or a list of
>>>>> processes/clients locking a particular file?
>>>>> And the million dollar question: is it possible to forcefully
>>>>> remove a lock?
>>>>>
>>>>> I'm using NFSv4 on Linux 2.6.18 (server and client).
>>>>>
>>>>>
>>>>>
>>>> *Cough* !
>>>>
>>>> Bruce, so what happens to my lock dropping patch that was said "will
>>>> get pulled into 2.6.26 kernel" ?
>>>>
>>>>
>>> Gulp.
>>>
>>> I started an alternative implementation, and got it to the point where
>>> it was basically working (but I didn't completely trust it). And I did
>>> a small fix or two on your patches, but I seem to recall there were one
>>> or more todo's there too.
>>>
>>> Then I dropped both for a couple weeks.
>>>
>>>
>> Be carefully. .. "a couple weeks" can turn into "a couple years" .. It
>> has been more than 2 years since my first patch submission. Regardless
>> the patch has been repeatedly requested and had gone thru thorough
>> testings, it just sits there idling while Linux nfs server keeps
>> suffering the very same issue.
>>
>
> Yes, apologies for not getting this done on time.
>
>
>> Don't get too ambitious. Cluster issues are not trivial - please take
>> one step at a time. The patch is very usable *and* solves an immediate
>> issue *and* has a clean boundary with existing main-line logic. I really
>> don't see the reason to delay it.
>>
>
> My current version of your patch follows.
>
> I've rebased it a couple times (the only change I recall being required
> was a trivial fix to take into account reorganization of struct
> nameidata.). I also made two other changes; any objections to either?:
>
Thanks for doing this... The changes look good - though I don't have
chances to test it out yet. When is 2.6.26 code cut-off date (or we have
missed it again) ?
-- Wendy
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-04-18 14:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 9:17 [NFS] Forcefully resetting a lock Erik Hensema / HostingXS Internet Services
[not found] ` <200804161117.24734.hensema-yolSOB3tinz/D1n+0JDH9g@public.gmane.org>
2008-04-16 11:44 ` Jeff Layton
2008-04-16 15:15 ` Wendy Cheng
2008-04-16 18:42 ` J. Bruce Fields
2008-04-16 19:39 ` Wendy Cheng
2008-04-17 21:52 ` J. Bruce Fields
2008-04-18 14:02 ` Wendy Cheng [this message]
2008-04-18 18:19 ` J. Bruce Fields
2008-04-22 23:15 ` J. Bruce Fields
2008-04-22 23:17 ` [NFS] [PATCH] lockd: unlock lockd locks associated with a given server ip J. Bruce Fields
2008-04-22 23:18 ` [NFS] [PATCH] lockd: unlock lockd locks held for a certain filesystem J. Bruce Fields
2008-04-23 2:57 ` Wendy Cheng
2008-04-23 7:44 ` Christoph Hellwig
2008-04-23 17:12 ` J. Bruce Fields
2008-04-23 17:52 ` Christoph Hellwig
2008-04-23 20:01 ` J. Bruce Fields
2008-04-23 20:39 ` Wendy Cheng
2008-04-23 21:02 ` J. Bruce Fields
2008-04-23 21:17 ` Wendy Cheng
2008-04-23 21:39 ` J. Bruce Fields
2008-04-23 21:44 ` Wendy Cheng
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=4808A9DE.9040304@gmail.com \
--to=s.wendy.cheng@gmail.com \
--cc=bfields@fieldses.org \
--cc=hensema-yolSOB3tinz/D1n+0JDH9g@public.gmane.org \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.