| Summary: | NFS filesystems are not mounted during boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vít Ondruch <vondruch> |
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | bfields, jdisnard, jlayton, steved |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-18 16:09:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Vít Ondruch
2011-09-22 09:22:07 UTC
Same problem. NFS shares for user home dirs specified in autofs maps. Uses unable to login after bootup.
It seems the nfs-lockd.service is running, but has the same problem described by Vít Ondruch. I was able to work-around the issue by stoppign at starting the service. Please note, simply restarting the service fails to work. Also, even though systemctl status indicates the service inoperable (and that is true) the PID file exists in /var/run/rpc.statd.pid, and the process was alive.
So the process had to be killed, and a new process created.
# systemctl stop nfs-lock.service
# systemctl start nfs-lock.service
# systemctl status nfs-lock.service
nfs-lock.service - NFS file locking service.
Loaded: loaded (/lib/systemd/system/nfs-lock.service; enabled)
Active: active (running) since Sun, 30 Oct 2011 22:22:28 -0500; 6s ago
Process: 26125 ExecStopPost=/sbin/sysctl -w fs.nfs.nlm_tcpport=0 fs.nfs.nlm_udpport=0 (code=exited, status=0/SUCCESS)
Process: 26162 ExecStart=/sbin/rpc.statd $STATDARG (code=exited, status=0/SUCCESS)
Process: 26158 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-lock.preconfig (code=exited, status=0/SUCCESS)
Main PID: 26164 (rpc.statd)
CGroup: name=systemd:/system/nfs-lock.service
â 26164 /sbin/rpc.statd
This should work on bootup.
(In reply to comment #1) > Same problem. NFS shares for user home dirs specified in autofs maps. Uses > unable to login after bootup. > > It seems the nfs-lockd.service is running, but has the same problem described > by Vít Ondruch. I was able to work-around the issue by stoppign at starting the > service. Please note, simply restarting the service fails to work. Also, even > though systemctl status indicates the service inoperable (and that is true) the > PID file exists in /var/run/rpc.statd.pid, and the process was alive. > > So the process had to be killed, and a new process created. Where there any type of failures logged in /var/log/messages? (In reply to comment #2) [snip] > > Where there any type of failures logged in /var/log/messages? I do not believe there were any syslogs related to the nfs-lockd at the time I reported in comment #1. The output of systemctl was the only clear indication of the problem statement. Also please note the process was there, the pid file existed. However the process didn't work, and systemctl said the start of the service failed. There is some good news. The issue seems to have gone away. What has changed? * the aforementioned systemctl stop/start nfs-lockd.service. * The system was not reset since the initial report. * To assist with the bugzilla the system was reset to have the issue reproduce. * yum update I was hoping Vít might try to reproduce my success with the systemctl stop/start of nfs-lockd. (In reply to comment #3) > (In reply to comment #2) > [snip] > > > > Where there any type of failures logged in /var/log/messages? > > I do not believe there were any syslogs related to the nfs-lockd at the time I > reported in comment #1. The output of systemctl was the only clear indication > of the problem statement. Also please note the process was there, the pid file > existed. However the process didn't work, and systemctl said the start of the > service failed. > > There is some good news. > The issue seems to have gone away. > > What has changed? > > * the aforementioned systemctl stop/start nfs-lockd.service. No... There is an upcoming change to ensure the network is up before the service is started... > > * The system was not reset since the initial report. This could be it.. > > * To assist with the bugzilla the system was reset to have the issue reproduce. Rebooting sometime does do magically things! 8-) > > * yum update This is always a good option... especially with an early release of a new version of Fedora... > > I was hoping Vít might try to reproduce my success with the systemctl > stop/start of nfs-lockd. Make my Day! ;-) At this point I'm going to close the bug as fixed... Please feel free to reopen if the problem comes back... |