Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionSteffen Froemer
2016-11-07 07:57:46 UTC
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?
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.