From: Christian Robottom Reis <kiko@acm.org>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: NFS List <linux-nfs@vger.kernel.org>
Subject: Re: Finding and breaking client locks
Date: Mon, 21 Mar 2016 17:56:38 -0300 [thread overview]
Message-ID: <20160321205637.GB5118@async.com.br> (raw)
In-Reply-To: <20160321175500.GA5118@async.com.br>
On Mon, Mar 21, 2016 at 02:55:00PM -0300, Christian Robottom Reis wrote:
> > Alternately, there is the /proc/fs/nfsd/unlock_ip interface. Supposedly
> > you can echo an address into there and it'll forcibly drop all of the
> > locks that that that client holds. I've not used that so YMMV there.
>
> Oh! That's a very interesting, and I now see it documented here:
>
> http://people.redhat.com/rpeterso/Patches/NFS/NLM/004.txt
On second look, I don't think that interface is meant to take a client
IP, but rather a server IP:
"They are intended to allow admin or user mode script to release NLM
locks based on either a path name or a server in-bound ip address[...]"
That's why echoing the client IP makes no difference.
I'm surprised -- so far I've found no facility for lock management
server-side other than restarting the server.
--
Christian Robottom Reis | [+55 16] 3376 0125 | http://async.com.br/~kiko
| [+55 16] 991 126 430 | http://launchpad.net/~kiko
next prev parent reply other threads:[~2016-03-21 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 14:39 Finding and breaking client locks Christian Robottom Reis
2016-03-21 17:19 ` Jeff Layton
2016-03-21 17:55 ` Christian Robottom Reis
2016-03-21 20:56 ` Christian Robottom Reis [this message]
2016-03-21 21:27 ` Jeff Layton
2016-03-22 0:09 ` Christian Robottom Reis
2016-03-22 0:30 ` J. Bruce Fields
2016-03-31 5:11 ` NeilBrown
2016-03-31 20:52 ` Frank Filz
2016-03-22 0:58 ` Christian Robottom Reis
2016-03-31 5:07 ` NeilBrown
2016-03-31 13:34 ` Trond Myklebust
2016-03-31 22:40 ` NeilBrown
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=20160321205637.GB5118@async.com.br \
--to=kiko@acm.org \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
/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