From: "Frank Filz" <ffilzlnx@mindspring.com>
To: "'J. Bruce Fields'" <bfields@fieldses.org>,
"'Jeff Layton'" <jlayton@kernel.org>
Cc: <steved@redhat.com>, <linux-nfs@vger.kernel.org>, <jfajerski@suse.com>
Subject: RE: [PATCH] manpage: explain why showmount doesn't really work against a v4-only server
Date: Mon, 13 May 2019 07:19:57 -0700 [thread overview]
Message-ID: <08d301d50996$f1cd84e0$d5688ea0$@mindspring.com> (raw)
In-Reply-To: <20190513134457.GA13359@fieldses.org>
> On Mon, May 13, 2019 at 09:29:42AM -0400, Jeff Layton wrote:
> > Yeah, that certainly wouldn't hurt. I'd suggest we add that in a
> > separate patch though.
>
> Agreed.
>
> > We will need to spell this out in the manpage either way. At least
> > with ganesha, you can export some filesystems via v3 and others via v4
> > only, and the MNT service there will only report the v3 ones. In that
> > case, you have a reachable service, but the v4-only filesystems will
> > be missing from showmount's output.
>
> That doesn't sound like a great idea to me, but maybe you have no choice
if for
> some reason you want to allow simultaneous support for v3-only clients and
for
> filesystems that require long filehandles? Ugh.
>
> Anyway, this kind of warning doesn't have to catch every odd case.
Good conversation.
Another thing worth noting in the warning also is that some servers (Ganesha
for sure) will not list exports to showmount that the client issuing the
showmount doesn't have access to (and for NFSv4 they won't show up in the
directory listing).
Obviously the warning can't be perfect, but at least highlighting that the
issue of what exports are visible is complicated.
Frank
next prev parent reply other threads:[~2019-05-14 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 21:54 [PATCH] manpage: explain why showmount doesn't really work against a v4-only server Jeff Layton
2019-05-11 13:54 ` J. Bruce Fields
2019-05-13 8:12 ` Jan Fajerski
2019-05-13 13:29 ` Jeff Layton
2019-05-13 13:44 ` J. Bruce Fields
2019-05-13 14:19 ` Frank Filz [this message]
2019-05-29 13:15 ` Steve Dickson
2019-05-29 13:24 ` J. Bruce Fields
2019-06-03 14:27 ` Steve Dickson
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='08d301d50996$f1cd84e0$d5688ea0$@mindspring.com' \
--to=ffilzlnx@mindspring.com \
--cc=bfields@fieldses.org \
--cc=jfajerski@suse.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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).