Hide Forgot
Description of problem: When the system has NFS-mounts in /etc/fstab, it will fail to boot. Version-Release number of selected component (if applicable): nfs-utils-1.3.0-0.21.el7_2.1.x86_64 How reproducible: Steps to Reproduce: 1. insert nfs mount to /etc/fstab nfs-server.example.com:/volume1 /nfs/vol1 nfs nosuid,vers=3,sec=sys,rw 0 0 2. reboot system Actual results: System fail to boot. Expected results: The system should boot normally. Additional info: Adding 'remote-fs-pre.target' to the After-section in systemd-services-unit will resolve this issue [Unit] Description=NFS status monitor for NFSv2/3 locking. DefaultDependencies=no Conflicts=umount.target Requires=nss-lookup.target rpcbind.target After=network.target nss-lookup.target rpcbind.service remote-fs-pre.target PartOf=nfs-utils.service Wants=nfs-config.service After=nfs-config.service [Service] EnvironmentFile=-/run/sysconfig/nfs-utils Type=forking PIDFile=/var/run/rpc.statd.pid ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS
(In reply to Steffen Froemer from comment #0) Hi Steffen, Have you ever tried the "_netdev" option ? MOUNT(8) <snip> _netdev 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). <snip/> > Steps to Reproduce: > 1. insert nfs mount to /etc/fstab > > nfs-server.example.com:/volume1 /nfs/vol1 nfs > nosuid,vers=3,sec=sys,rw 0 0 update to try with this: nfs-server.example.com:/volume1 /nfs/vol1 nfs _netdev,nosuid,vers=3,sec=sys,rw 0 0 ^^^^^^^^ Thanks
Adding devel ack as this should be looked at for 7.4. It is however marked low priority but on the RPL which is a bit of a contradiction. Mark, do you want us to increase the priority on this one, or should we take it off the RPL?
Raise the priority. It's a 'fail to boot' situation with two customer cases logged against it. Probably shouldn't be low priority in any case. I've increased both priority and severity to high since it effects booting a system.
The problems does not exist with nfs-utils-1.3.0-0.34.el7 Adding rhel7srv:/home/src /home/src nfs nosuid,vers=3,sec=sys,rw 0 0 to /etc/fstab and rebooting worked as expected Also I'm not sure it makes send to add remote-fs-pre.target to the rpc-statd.service file since that will cause NFS mounts to occur. Those mounts will also cause rpc.statd be started. what nfs-utils version are you seeing this with?
Looking at the logs I don't see any problem wrt dependencies. Mount unit is started after network interface is configured.
Customer is no longer able to reproduce the issue and because of that we are unable to obtain further information that would help us to root-cause the issue.