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: mount.nfs4 and logging
To:     linux-nfs@vger.kernel.org
References: <S1725851AbgIKKt5/20200911104957Z+185@vger.kernel.org>
From:   Chris Hall <linux-nfs@gmch.uk>
Message-ID: <a38a1249-c570-9069-a498-5e17d85a418a@gmch.uk>
Date:   Fri, 11 Sep 2020 12:45:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <S1725851AbgIKKt5/20200911104957Z+185@vger.kernel.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk


I have a client and server configured for nfs4 only.

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

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 ?  Or otherwise find a way to 
discover why the "Protocol not supported" message is being issued ?

Thanks,

Chris