Re: nfs shares not mounted at boot

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

 



This poroblem occurs on other unices as well, try using the bg option in your 
nfs fstab entry.
Andy
On Sunday 22 February 2015 21:39:13 Pete Travis wrote:
> On Feb 22, 2015 1:01 AM, "Jens Neu" <jens@xxxxxxxxxx> wrote:
> > Dear list,
> > 
> > maybe since 2 weeks (close to upgrade to Twenty_One), my nfs shares are
> 
> no longer mounted at boot. Claims that the nfs server is not resolvable,
> but it clearly is. Raised the timeo to 200, but no luck. Hints? Bugworthy?
> 
> > regards Jens
> > 
> > [root@andrea ~]# systemctl status media-jessa.mount
> > ● media-jessa.mount - /media/jessa
> > 
> >    Loaded: loaded (/etc/fstab)
> >    Active: failed (Result: exit-code) since Sun 2015-02-22 08:52:55 CET;
> 
> 1min 15s ago
> 
> >     Where: /media/jessa
> >     
> >      What: mavie.zeeroos.int:/media/jessa
> >      Docs: man:fstab(5)
> >      
> >            man:systemd-fstab-generator(8)
> >   
> >   Process: 1849 ExecMount=/bin/mount -n mavie.zeeroos.int:/media/jessa
> 
> /media/jessa -t nfs -o
> _netdev,rw,hard,intr,nfsvers=3,tcp,noatime,nodev,async,rsize=8192,wsize=8192
> ,vers=3,nolock,timeo=200 (code=exited, status=32)
> 
> > Feb 22 08:52:55 andrea.zeeroos.de systemd[1]: media-jessa.mount mount
> 
> process exited, code=exited status=32
> 
> > Feb 22 08:52:55 andrea.zeeroos.de systemd[1]: Failed to mount
> 
> /media/jessa.
> 
> > Feb 22 08:52:55 andrea.zeeroos.de systemd[1]: Unit media-jessa.mount
> 
> entered failed state.
> 
> > Feb 22 08:52:55 andrea.zeeroos.de mount[1849]: mount.nfs: Failed to
> 
> resolve server mavie.zeeroos.int: Name or service...known
> 
> > Hint: Some lines were ellipsized, use -l to show in full.
> > 
> > 
> > [root@andrea ~]# host mavie.zeeroos.int
> > mavie.zeeroos.int has address 192.168.17.124
> > mavie.zeeroos.int has IPv6 address 2001:6f8:11d5:0:215:17ff:fe36:aa4e
> > 
> > 
> > --
> 
> I use a the systemd automount functionality to mount NFS shares on demand.
> Use "x-systemd.automount" as one of the mount options and the problem will
> go away.  Bonus, if the network is legitimately down, it doesn't hold up
> booting.
> 
> `man systemd.mount` explains,
> http://www.freedesktop.org/software/systemd/man/systemd.mount.html .
> 
> --Pete

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[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