Bug 703852
| Summary: | NFS mounts not getting mounted automatically during start-up | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jay Turner <jturner> | ||||||||||||||||
| Component: | systemd | Assignee: | systemd-maint | ||||||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||
| Priority: | medium | ||||||||||||||||||
| Version: | 15 | CC: | fche, johannbg, johannbg, lpoetter, metherid, mschmidt, notting, plautrba, srevivo, tilmann | ||||||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | i686 | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | |||||||||||||||||||
| : | 710502 (view as bug list) | Environment: | |||||||||||||||||
| Last Closed: | 2012-01-24 18:52:05 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Embargoed: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
Created attachment 498288 [details]
F15 messages
Look for "/mnt/partners" and "/mnt/ginger" in the attached log files. Hi Jay, Could you please boot with "log_buf_len=1M systemd.log_target=kmsg systemd.log_level=debug" and attach the output of "dmesg"? Thanks. Oddly enough, I have done a number of reboots today and am not seeing the mount problem. I did have one boot where the nfslock service failed to start, but have been unable to reproduce that as well. Closing this out. Will reopen if the problem surfaces again. I have the exact same issue. Please find all log files attached. Additionally I found out, that logging into gnome (as root) and using nm-applet to turn ethernet off and on again results in /home from NFS being mounted. Created attachment 502364 [details]
dmesg output with systemd.log_level=debug
Created attachment 502365 [details]
/proc/self/mounts
Created attachment 502366 [details]
/etc/fstab
I use NetworkManager-0.8.9997-1.git20110531.fc15.i686 systemd-26-2.fc15.i686 systemd-sysv-26-2.fc15.i686 systemd-units-26-2.fc15.i686 Here are some additional infos: [root@sam ~]# systemctl status home.mount home.mount - /home Loaded: loaded Active: active (mounted) since Wed, 01 Jun 2011 21:38:34 +0200; 16min ago Where: /home What: /dev/sda7 CGroup: name=systemd:/system/home.mount Created attachment 502368 [details]
systemctl show home.mount output
(In reply to comment #6) > dmesg output with systemd.log_level=debug I see two problems: 1. Something gets mounted on /home even before the network is started. It must be the sandbox service. Try disabling it. 2. NetworkManager-wait-online.service is not working as expected. It quits immediately with a failure: [ 21.703189] systemd[1]: Job NetworkManager.service/start finished, result=done [ 21.706765] systemd[1]: About to execute: /usr/bin/nm-online -q -x --timeout=30 [ 21.723075] systemd[1]: Forked /usr/bin/nm-online as 814 [ 21.726549] systemd[1]: NetworkManager-wait-online.service changed dead -> start [ 21.865662] r8169 0000:02:00.0: em1: link down [ 21.868962] r8169 0000:02:00.0: em1: link down [ 21.872380] ADDRCONF(NETDEV_UP): em1: link is not ready [ 22.011777] systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus [ 22.016442] systemd[1]: Received SIGCHLD from PID 814 (nm-online). [ 22.019876] systemd[1]: Got SIGCHLD for process 814 (nm-online) [ 22.023156] systemd[1]: Child 814 died (code=exited, status=1/FAILURE) [ 22.026386] systemd[1]: Child 814 belongs to NetworkManager-wait-online.service [ 22.029609] systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1 The link is not ready yet, therefore NM is not connecting. "-x" was passed to nm-online, so it quits. That's why the original NM initscript did something similar to: ExecStart=/bin/sh -c 'nm-online -q --timeout=10 || nm-online -q -x --timeout=30' (which is what I originally proposed for NetworkManager-wait-online.service) > 2. NetworkManager-wait-online.service is not working as expected. It quits > immediately with a failure: Filed as bug 710502 /home is now mounted after "systemctl disable sandbox.service" and a reboot. Please find attached the systemd.log. Created attachment 502858 [details]
dmesg output with systemd.log_level=debug after disabling sandbox
With a disabled sandbox service, /home is mounted sucessfully.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Is this still a problem or can this bug be closed? I checked it with a fresh install of F16 and everything runs smoothly. No problem mounting NFS shares in /etc/fstab. There is also no need to disable the sandbox service as written above. FWIW, I'm seeing what seems like a recurrence of this problem on rawhide;
systemctl status home.mount sez:
home.mount - /home
Loaded: loaded (/etc/fstab)
Active: active (mounted) (Result: exit-code) since Mon 2013-05-27 11:17:59 EDT; 16min ago
Where: /home
What: super:/home
Process: 248 ExecMount=/bin/mount super:/home/ /home -t nfs -o ro,bg,hard,intr (code=exited, status=32)
(where 'super' is an ipv4 host listed in /etc/hosts). A manual run of that command eventually mounts the filesystem, but complains of various rpc services being absent. It's as though those various .want symlinks are not set right.
|
Created attachment 498286 [details] boot.log for F15 system Description of problem: I have a couple of nfs mounts listed in fstab as "auto" and yet both are failing to be mounted during F15 boot. I tried the "systemctl enable NetworkManager-wait-online.service" trick, but that had no impact on the issue. Version-Release number of selected component (if applicable): # rpm -q systemd nfs-utils NetworkManager systemd-26-1.fc15.x86_64 nfs-utils-1.2.3-11.fc15.x86_64 NetworkManager-0.8.999-2.git20110509.fc15.x86_64 How reproducible: Every boot. Steps to Reproduce: 1. Boot up a system with NetworkManager controlling networking and a few "auto" mounts listed in fstab. Actual results: "auto" mounts will not be automatically mounted; they will mount successfully post-boot with "mount -a" Expected results: "auto" mounts should be mounted automatically Additional info: