linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
	Cedric Blancher <cedric.blancher@gmail.com>
Cc: Peter Scott <pjscott@jpl.nasa.gov>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 file lock reporting interface request
Date: Tue, 7 Aug 2018 16:05:42 -0500	[thread overview]
Message-ID: <f72df1af-1d8e-9203-0587-0e7b4a7db9aa@opengridcomputing.com> (raw)
In-Reply-To: <20180807203419.GB18415@fieldses.org>

Hi Bruce,

FWIW, I don't think dtrace does/did what NASA is asking for, but that's 
really irrelevant. The locks in NFSv4 are application specific locks, 
not generic kernel locks, so a service looking for spinlocks, mutexes, 
etc... wouldn't really be helpful I don't think.  However implementing a 
/sys/class, debugfs thingy that dumped the nfsv4 locks held is fairly 
simple, although I would think there are security implications.

Tom

On 8/7/2018 3:34 PM, J. Bruce Fields wrote:
> On Thu, Aug 02, 2018 at 08:50:20PM +0200, Cedric Blancher wrote:
>> Solaris and FreeBSD dtrace facility supports this functionality.
>> Unfortunately, Linux rejected dtrace for license issues, and instead
>> did... nothing.
> I didn't think was this sort of question tracing was designed to
> answer--it's a question about the system state at a given time (who
> holds what locks), rather than a list of events.  But I know nothing
> about dtrace.
>
> --b.
>
>> 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
>> --
>> 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
> --
> 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

-- 
Thomas Tucker
President
Open Grid Computing, Inc.
(m) 512-826-7622
(o) 512-220-3434


  parent reply	other threads:[~2018-08-07 23:28 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
2018-08-07 20:34   ` J. Bruce Fields
2018-08-07 20:53     ` Scott Mayhew
2018-08-07 21:05     ` Tom Tucker [this message]
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=f72df1af-1d8e-9203-0587-0e7b4a7db9aa@opengridcomputing.com \
    --to=tom@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=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).