FS#47309 - [systemd] Boot freezes with "A start job is running for Create Volatile Files and Directories"
Attached to Project:
Arch Linux
Opened by Lucas Simões (kaslusimoes) - Wednesday, 09 December 2015, 19:19 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 12 June 2016, 19:17 GMT
Opened by Lucas Simões (kaslusimoes) - Wednesday, 09 December 2015, 19:19 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 12 June 2016, 19:17 GMT
|
Details
Description:
We have a LAN where the main Debian server has some NFS (version 3) partitions. These partitions are mounted on every other machine on the network, which use Arch. When upgrading from systemd v227 to systemd v228, the following message appeared during boot: "A start job is running for Create Volatile Files and Directories" and we get stuck in the boot screen. A workaround is not to mount the NFS partitions, or revert systemd to the previous version. Mounting manually after boot isn't a problem. We are using the following mount flags: vers=3,bg,acl,x-systemd.automount,x-systemd.device-timeout=10,tcp,wsize=16384,rsize=16384 Steps to reproduce: - Mount a remote NFS v3 partition (on fstab) - Upgrade systemd - Reset |
This task depends upon
Closed by Dave Reisner (falconindy)
Sunday, 12 June 2016, 19:17 GMT
Reason for closing: Upstream
Additional comments about closing: https://github.com/systemd/systemd/issue s/1959
Sunday, 12 June 2016, 19:17 GMT
Reason for closing: Upstream
Additional comments about closing: https://github.com/systemd/systemd/issue s/1959
For now, I've created a file named remote-mount.service in /etc/systemd/system/ containing the following:
[Unit]
Description=Mount /MOUNTPOINT
[Service]
Type=oneshot
ExecStart=/usr/bin/mount /MOUNTPOINT
Then I did:
systemctl enable remote-mount
systemctl start remote-mount
And that seems to bring up the NFS file system on boot. It's ugly, though.