On Wed, Jun 10, 2020 at 1:40 AM Stephen Morris <samorris(a)netspace.net.au> wrote:
On 10/6/20 7:12 am, Tom H wrote:
> On Tue, Jun 9, 2020 at 1:55 PM Stephen Morris <samorris(a)netspace.net.au> wrote:
>> I have the following statement in fstab:
>>
>> 192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs
>> nfsvers=1,x-systemd.automount,defaults 0 0
>>
>> When I issue the command 'mount /mnt/nfs' it fails with the
>> following messages shown in dmesg, which indicate that the mount
>> seems to be trying to proceed via nfs4, why is it doing this when I
>> have the option nfsvers=1?
>>
>> [48439.472418] FS-Cache: Netfs 'nfs' registered for caching
>> [48439.472732] *** VALIDATE nfs ***
>> [48439.472741] *** VALIDATE nfs4 ***
>> [48439.476329] Key type dns_resolver registered
>> [48439.639981] NFS: Registering the id_resolver key type
>> [48439.639993] Key type id_resolver registered
>> [48439.639994] Key type id_legacy registered
>> [48439.844036] NFS4: Couldn't follow remote path
>> [48439.852856] NFS4: Couldn't follow remote path
>> [48439.898650] NFS4: Couldn't follow remote path
>> [48480.763754] NFS4: Couldn't follow remote path
>> [48480.774645] NFS4: Couldn't follow remote path
>
> nfsv1 has never existed. Use "nfsvers=3" or "nfsvers=4".
In another thread to Roger I've mentioned that in F28, and even
though I didn't specify it, probably F30, Fedora used nfs4 by default
Indeed, nfsv4 has been the default for many releases. So it makes
sense that the mount would fallback to nfsv4 if the requested version
isn't available.
which would not enable mounting of my nas, I had to specify
nfsvers=1
in the mount instruction in fstab for the nas to be mounted, which
now seems to no longer work. Following your suggestion I have tried
nfsvers=3 and that has enabled the nas to be mounted.
I'm glad that "nfsvers=3" is working. Are you sure that you're not
misremembering "nfsvers=1"?