Bug 675680

Summary:	hang during mount of nfs
Product:	[Fedora] Fedora	Reporter:	Marcela Mašláňová <mmaslano>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	fche, lpoetter, metherid, mschmidt, notting, plautrba
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-02-16 23:04:24 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:

Description Marcela Mašláňová 2011-02-07 09:51:44 UTC

Hang after trying mount nfs during boot. For unknown reason NM didn't start my network, so nfs can't be mounted. 

Network was working before last boot, so I have the correct symlinks. The real problem is that network services should be started after network is up. In this case it tries to mount something what can't be accessible and what's more it hangs without any possibility to skip this part. Hang after unsuccessful mount is the wrong thing. It can't be skip in any way, so a/ make it somehow "skipable", b/timeout for mount, c/correct system solution because more services can have problems.

Comment 1 Marcela Mašláňová 2011-02-07 09:54:48 UTC

Output from console:
systemd: Unit readahead-replay.service entered failed state.
systemd: Unit mnt-myserver.mount entered failed state.
systemd: mnt-myserver.mount mount process exited, code=exited status=1
systemd: Unit mnt-myserver2.mount entered failed state.
systemd: mnt-myserver2.mount mount process exited, code=exited status=1

Comment 2 Michal Schmidt 2011-02-07 13:45:18 UTC

In systemd there is a timeout for services and for mounts too. The fact that you're getting the "Unit ... entered failed state" messages suggests that systemd did indeed give up on these mounts.

So it is not at all clear to me what it is waiting for then. Would you perhaps get more information if you boot with "systemd.log_level=debug systemd.log_target=kmsg" (and without "quiet")?

Comment 3 Lennart Poettering 2011-02-16 22:55:45 UTC

*** Bug 672389 has been marked as a duplicate of this bug. ***

Comment 4 Lennart Poettering 2011-02-16 23:04:24 UTC


*** This bug has been marked as a duplicate of bug 645805 ***