Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: mount.nfs4 and logging
To:     Chris Hall <linux-nfs@gmch.uk>, linux-nfs@vger.kernel.org
References: <S1725851AbgIKKt5/20200911104957Z+185@vger.kernel.org>
 <a38a1249-c570-9069-a498-5e17d85a418a@gmch.uk>
From:   Steve Dickson <SteveD@RedHat.com>
Message-ID: <f06f86ef-08bd-3974-3d92-1fbda700cc11@RedHat.com>
Date:   Mon, 14 Sep 2020 14:30:35 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <a38a1249-c570-9069-a498-5e17d85a418a@gmch.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

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.