Bug 89365

Summary:	remote-fs.target not executed at boot in 219
Product:	systemd	Reporter:	Andreas Radke <andyrtr>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED NOTOURBUG	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium	CC:	bjo, jjardon
Version:	unspecified
Hardware:	All
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	bootlog_218 bootlog_219

Description Andreas Radke 2015-02-27 19:04:33 UTC

Created attachment 113877 [details]
bootlog_218

ArchLinux user report broken mounting remote fs fstab entries since systemd 219 (nfs,sshfs and maybe more). The mount command itself seems not to be executed at all. After boot the filesystem can be mounted from command line with success.

Downstream report: https://bugs.archlinux.org/task/43915

Attaching debug logs for boot with v218 and v219.

218 successfully executes remote-fs-pre.target and remote-fs.target while 219 ends here:

Feb 27 19:28:32 workstation64 systemd[1]: remote-fs-pre.target changed dead -> active
Feb 27 19:28:32 workstation64 systemd[1]: Job remote-fs-pre.target/start finished, result=done
Feb 27 19:28:32 workstation64 systemd[1]: Reached target Remote File Systems (Pre).
Feb 27 19:28:32 workstation64 systemd-logind[282]: Got message type=signal sender=:1.1 destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=183 reply_cookie=0 error=n/a
Feb 27 19:28:32 workstation64 systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=183 reply_cookie=0 error=n/a
Feb 27 19:28:32 workstation64 systemd[1]: Starting Remote File Systems (Pre).
Feb 27 19:28:32 workstation64 systemd-logind[282]: Got message type=signal sender=:1.1 destination=n/a object=/org/freedesktop/systemd1/unit/remote_2dfs_2dpre_2etarget interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=184 reply_cookie=0 error=n/a
Feb 27 19:28:32 workstation64 systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/remote_2dfs_2dpre_2etarget interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=184 reply_cookie=0 error=n/a
Feb 27 19:28:32 workstation64 systemd-logind[282]: Got message type=signal sender=:1.1 destination=n/a object=/org/freedesktop/systemd1/unit/nfs_2dclient_2etarget interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=185 reply_cookie=0 error=n/a
Feb 27 19:28:32 workstation64 systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/nfs_2dclient_2etarget interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=185 reply_cookie=0 error=n/a

Comment 1 Andreas Radke 2015-02-27 19:05:26 UTC

Created attachment 113878 [details]
bootlog_219

Comment 2 exi+freedesktop 2015-03-07 10:08:39 UTC

I can confirm this.

My .automount unit for nfs is in the "inactive (dead)" state after boot.
All other .automount units work without problems.

systemd 218 works without problems.

Comment 3 Andreas Radke 2015-03-16 14:54:16 UTC

This seems to be not a real bug but a change in default installation behaviour. With v219 "remote-fs.target" isn't enabled anymore by default. Enabling this target seems to fix all mounting issues at boot. At least my nfs share get properly mounted.

Comment 4 Lennart Poettering 2015-05-15 14:27:20 UTC

It's really a job for the downstream distros to enable remote-fs.target on first install. Fedora for example does this in %post in the RPM scriptlets.

This appears to be something to fix in your distro...

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.