Re: NFS Mount Point Failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry, you are confusing the option not causing an issue with it
actaully selecting version=1.

The option may not have caused an issue on f28, but as wikipedia says
and someone else says there never was NFS version 1 (on linux).  It
would seem the behavior when you give it an incorrect mount now causes
it to actually fail, and did not before.

Note I just checked on an old RHEL4 and RHEL5 box (2.6.9/2.6.18
kernel, I believe RHEL4 is based off of Fedora Core 3) and the man
pages says this on both.

   Three different versions of the NFS protocol are supported by the
Linux NFS client: NFS version 2, NFS version 3, and NFS version 4.  To
mount via NFS version 2, use the nfs  file  system
       type  and  specify nfsvers=2.  To mount via NFS version 3, use
the nfs file system type and specify nfsvers=3.  Version 3 is the
default protocol version for the nfs file system type when
       nfsvers= is not specified on the mount command.  To mount via
NFS version 4, use the nfs4 file system type.  The nfsvers= keyword is
not supported for the nfs4 file system type.

So many years prior to F28 there was no mention of 1 existing.

On Tue, Jun 9, 2020 at 6:40 PM Stephen Morris <samorris@xxxxxxxxxxxxxxx> wrote:
>
> On 10/6/20 7:12 am, Tom H wrote:
> > On Tue, Jun 9, 2020 at 1:55 PM Stephen Morris <samorris@xxxxxxxxxxxxxxx> 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".
> Hi Tom, 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
> 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. Now I have to try
> and figure out the right specification for the cifs mount point to be
> able to be mounted via the Windows share exposed by the nas. Thankyou
> for all your help.
>
> regards,
> Steve
>
> > _______________________________________________
> > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux