From: Cedric Blancher <cedric.blancher@gmail.com>
To: Peter Scott <pjscott@jpl.nasa.gov>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 file lock reporting interface request
Date: Thu, 2 Aug 2018 20:50:20 +0200 [thread overview]
Message-ID: <CALXu0UdHWGOnMYk-xGG6_GWGfdpXffc0U-+Ark0joEYvhPSh_g@mail.gmail.com> (raw)
In-Reply-To: <8dd8a352-aaca-71af-aca7-9be6c7039ff4@jpl.nasa.gov>
Solaris and FreeBSD dtrace facility supports this functionality.
Unfortunately, Linux rejected dtrace for license issues, and instead
did... nothing.
Ced
On 10 July 2018 at 04:28, Peter Scott <pjscott@jpl.nasa.gov> wrote:
> Hello. I am with the institutional hosting service at NASA's Jet Propulsion
> Laboratory and we have been trying to find the answer to an apparently
> simple question.
>
> We are running an NFSv4 server on Centos 7 and we need to get the server to
> tell us which files it thinks are locked by which clients. This is because
> we have observed failure modes where something apparently has a lock
> (because attempting to lock the file again blocks) but we can't find a
> client that has the lock. Finding out what the server believes would be
> critical to troubleshooting this.
>
> We tracked down Trond Myklebust and Neil Brown and conversation suggests
> that this is a function that is (a) not currently available and (b)
> reasonable to ask for. So this is me suggesting that an interface be
> provided to have knfsd output its list of locked files and clients.
>
> Regards,
> Peter Scott
> Office of the CIO
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
next prev parent reply other threads:[~2018-08-02 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 2:28 NFSv4 file lock reporting interface request Peter Scott
2018-08-02 14:14 ` J. Bruce Fields
2018-08-02 18:50 ` Cedric Blancher [this message]
2018-08-07 20:34 ` J. Bruce Fields
2018-08-07 20:53 ` Scott Mayhew
2018-08-07 21:05 ` Tom Tucker
2018-08-07 21:16 ` J. Bruce Fields
2018-08-15 17:35 ` 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=CALXu0UdHWGOnMYk-xGG6_GWGfdpXffc0U-+Ark0joEYvhPSh_g@mail.gmail.com \
--to=cedric.blancher@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pjscott@jpl.nasa.gov \
/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;
as well as URLs for NNTP newsgroup(s).