Linux NFS development
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Are there really no server-side mount/umount message for NFSv4?
Date: Tue, 21 Jul 2015 12:03:38 -0400	[thread overview]
Message-ID: <20150721160338.GD11050@fieldses.org> (raw)
In-Reply-To: <55AE4FC6.6050001@bio.ifi.lmu.de>

On Tue, Jul 21, 2015 at 03:57:26PM +0200, Frank Steiner wrote:
> we are missing the "authenticated u/mount request..." messages or 
> error messages like "refused mount request from /x (/): not exported"
> for NFSv4 servers. We were using the mount/umount messages e.g. to 
> detect when some reached a certain point of an installation etc.
> And the error messages on the server side often were more helpful
> than the ones on the client.
> 
> Is there really no way to get these easy-to-understand messages? 
> Debugging shows a lot but nothing that e.g. gives an understandable
> error reason.

There aren't any mount or umount calls in the NFSv4 protocol.

(For example, an NFSv4 server typically wouldn't have any way to tell
the difference between a client that has unmounted and one that just
isn't using the filesystem right now.)

If you could describe in more detail your use case, someone might be
able to suggest a different solution.  Or it might influence what sort
of information the nfs server exports to users in the future.

--b.

  reply	other threads:[~2015-07-21 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 13:57 Are there really no server-side mount/umount message for NFSv4? Frank Steiner
2015-07-21 16:03 ` J. Bruce Fields [this message]
2015-07-22  7:31   ` Mkrtchyan, Tigran
2015-07-22 14:34     ` J. Bruce Fields
2015-07-22 12:13   ` Frank Steiner
2015-07-22 14:33     ` 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=20150721160338.GD11050@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=fsteiner-mail1@bio.ifi.lmu.de \
    --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