On Mon, 2018-07-30 at 22:57 +0800, Ed Greshko wrote: > On 07/30/18 22:40, Bob Goodwin wrote: > > I have two computers, Fedora 27 and 28 that do not mount the nfs server at boot. It > > works from root afterward without any difficulty but that is a bit of an > > inconvenience. I put up with that problem with the Samba server for a long time but > > two is too much! > > > > This problem was unknown until I built this nfs box which pretty much says I've > > done something wrong but I have no idea what ... /etc/exports is: > > > > [bobg@ASRock-J3455M ~]$ cat /etc/exports > > /home/exports 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check,fsid=0) > > > > The client /etc/fstab is: > > > > 192.168.1.86:/home/exports /mnt/testb nfs4 defaults 0 0 > > > > Any suggestions appreciated, > > > > In your fstab you can try changing it to something like.... > > 192.168.1.86:/home/exports /mnt/testb nfs4 > rw,soft,intr,fg,comment=systemd.automount 0 0 > > You may not see it mounted at boot time but as soon as you access the directory it > will become mounted. > > At least that is the way I fixed a problem with NFS mounts of a NAS. > > _______________________________________________ > Is adding the _netdev option to fstab line worth a try? man mount The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system). _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/FZURJA32BIJLDHDMF2ES27VAV4OODKHS/
