Bug 773078
| Summary: | NFS mounts not always mounted at boot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rasmus Ory Nielsen <ron> | ||||
| Component: | nfoview | Assignee: | Steve Dickson <steved> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | bfields, fedora, jlayton, johannbg, mail, metherid, mschmidt, notting, plautrba, steved, systemd-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-19 14:11:29 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: |
|
||||||
|
Description
Rasmus Ory Nielsen
2012-01-10 21:04:16 UTC
Created attachment 551935 [details]
dmesg with systemd logging enabled (/mgsraw failed this time)
[ 49.653334] systemd[1]: Received SIGCHLD from PID 1123 (rpc.statd). [ 49.653371] systemd[1]: Got SIGCHLD for process 1123 (rpc.statd) [ 49.653445] systemd[1]: Child 1123 died (code=exited, status=1/FAILURE) [ 49.664238] FS-Cache: Loaded [ 49.686584] FS-Cache: Netfs 'nfs' registered for caching [ 49.687988] mount[1083]: mount.nfs: No such device [ 49.688272] systemd[1]: Received SIGCHLD from PID 1083 (mount). [ 49.688305] systemd[1]: Got SIGCHLD for process 1083 (mount) [ 49.688369] systemd[1]: Child 1083 died (code=exited, status=32/n/a) [ 49.688375] systemd[1]: Child 1083 belongs to mgsraw.mount I don't know the reason of these failures, but it looks like it has more to do with nfs-utils than systemd itself. Reassigning. Maybe it is fixed by: https://admin.fedoraproject.org/updates/nfs-utils-1.2.5-5.fc16 Thanks, I will do some testing, stay tuned Good news! I have been doing some tests, and the problem seems to have gone away. However, I can not tell which update that made the difference. Because, since submitting the bug report, I haven't paid attention to the problem. Instead I just added a cron @reboot statement to make sure all nfs mounts were active. But, even though my tests shows, that with a fully updated system all nfs mount points works, there's still a little quirk - some or all of the mount points are not mounted immediately. Those missing will appear exactly 60 seconds after reboot (systemd-analyze blame confirms this). Luckily the nfs-utils-1.2.5-5 update fixes this problem! I will do some more testing, but for now it certainly looks this this bug has been squashed. Thanks I forgot to add, that after installing the nfs-utils update, 'systemd-analyze blame' shows initialization times for the nfs mount points in the range 20-50ms. (In reply to comment #5) > I forgot to add, that after installing the nfs-utils update, 'systemd-analyze > blame' shows initialization times for the nfs mount points in the range > 20-50ms. Is this good or bad? Also can we close out this bz? tia.. Sorry for being unclear. 20-50ms is good, compared to before the nfs-utils update, where it often took about about 60000ms. I think we can close this bz. What's the correct status: closed/currentrelease? Thanks. It could be explained by the fixing of bug 786050. *** This bug has been marked as a duplicate of bug 786050 *** |