From: Steve Dickson <SteveD@RedHat.com>
To: Chris Hall <linux-nfs@gmch.uk>, linux-nfs@vger.kernel.org
Subject: Re: mount.nfs4 and logging
Date: Mon, 14 Sep 2020 14:30:35 -0400 [thread overview]
Message-ID: <f06f86ef-08bd-3974-3d92-1fbda700cc11@RedHat.com> (raw)
In-Reply-To: <a38a1249-c570-9069-a498-5e17d85a418a@gmch.uk>
Hello,
On 9/11/20 7:45 AM, Chris Hall wrote:
>
> I have a client and server configured for nfs4 only.
Would you mind sharing this configuration? Privately if
that works better...
I'm thinking that is a good direction to go towards
so maybe we make this configuration the default??
>
> The configuration used to work.
>
> I have just upgraded from Fedora 31 to 32 on the client. I now get:
>
> # mount /foo
> mount.nfs4: Protocol not supported
I've been trying to keep the versions the same... hopefully
nothing has broken in f31... ;-(
>
> Wireshark does not detect any attempt by the client to talk to the server.
>
> I get the same result if I do mount.nfs4 directly.
>
> Can I wind up the logging for mount.nfs4 ?
What server are you using?
> Or otherwise find a way to discover why the "Protocol not supported" message is being issued ?
Does rpcdebug -m nfs -s mount and mount -vvv show anything?
steved.
next prev parent reply other threads:[~2020-09-14 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1725851AbgIKKt5/20200911104957Z+185@vger.kernel.org>
2020-09-11 11:45 ` mount.nfs4 and logging Chris Hall
2020-09-14 18:30 ` Steve Dickson [this message]
2020-09-15 13:06 ` Chris Hall
2020-09-16 12:52 ` Kenneth Dsouza
2020-09-16 14:31 ` Kenneth Dsouza
2020-09-16 17:31 ` Kenneth Dsouza
2020-09-19 16:33 ` J. Bruce Fields
2020-09-19 16:40 ` J. Bruce Fields
[not found] ` <12298172-f830-4f22-8612-dfbbc74b8a40@gmch.uk>
2020-09-20 19:32 ` J. Bruce Fields
2020-09-21 14:40 ` Chris Hall
2020-09-23 14:40 ` 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=f06f86ef-08bd-3974-3d92-1fbda700cc11@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@gmch.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.