From: Christian Robottom Reis <kiko@acm.org>
To: NFS List <linux-nfs@vger.kernel.org>
Subject: Finding and breaking client locks
Date: Mon, 21 Mar 2016 11:39:14 -0300 [thread overview]
Message-ID: <20160321143914.GA6397@anthem.async.com.br> (raw)
Hello there,
I run a diskless network where every user NFS mounts pretty much
everything including /home and /var/mail. It's often the case that a
misbehaved client will leave a locked file stuck on the server -- today
it is a file in a user's mail/ directory.
Is there a way to query what files are being held locked by clients? I'm
sure the kernel knows, as it is able to enforce the lock, but it isn't
obvious how to extract that information -- lsof is documented to and
indeed does not return any information pertaining NFS client locks, and
I'm not clear whether /proc/locks (on the server side obviously) does or
not.
A related question is whether it is possible to break a client lock
without rebooting the server (or restarting the NFS services).
Does anyone have any insight to share? Thanks,
--
Christian Robottom Reis | [+55 16] 3376 0125 | http://async.com.br/~kiko
| [+55 16] 991 126 430 | http://launchpad.net/~kiko
next reply other threads:[~2016-03-21 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 14:39 Christian Robottom Reis [this message]
2016-03-21 17:19 ` Finding and breaking client locks Jeff Layton
2016-03-21 17:55 ` Christian Robottom Reis
2016-03-21 20:56 ` Christian Robottom Reis
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=20160321143914.GA6397@anthem.async.com.br \
--to=kiko@acm.org \
--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