Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47226 - Boot process hangs on "a start job is running for Create Volatile files and directories"
Attached to Project:
Community Packages
Opened by Juho Rutila (jrutila) - Monday, 30 November 2015, 21:32 GMT
Last edited by Dave Reisner (falconindy) - Monday, 30 November 2015, 21:51 GMT
Opened by Juho Rutila (jrutila) - Monday, 30 November 2015, 21:32 GMT
Last edited by Dave Reisner (falconindy) - Monday, 30 November 2015, 21:51 GMT
|
DetailsDescription:
When booting the boot process hangs on a message "a start job is running for Create Volatile files and directories" from systemd-tmpfiles-setup. When booted with "rescue" it goes to the rescue shell and the systemd-tmpfiles-setup is correctly (and fast) loaded. Same with emergency. Checked with tune2fs that the root filesystem had acl enabled and also forced it also through /etc/fstab. Did not help. /tmp is not bloated. Downgrading to systemd-227 resolved the issue. Additional info: * systemd-228-3 Steps to reproduce: 1. Upgrade systemd to 228-3 2. Reboot Result: Reboot process hangs on "a start job is running for Create Volatile files and directories". Ctrl-Alt-Del reboots. Expected: Reboot goes fastly and systemd-tmpfiles-setup is active and loaded correctly Workaround: downgrade systemd to 227-1 (tested) Other resources from the web: http://forums.debian.net/viewtopic.php?f=10&t=118008 https://bugs.archlinux.org/task/45813 (had to do with the kernel, I think) https://wiki.archlinux.org/index.php/Systemd#systemd-tmpfiles-setup.service_fails_to_start_at_boot |
This task depends upon
My /home is a NFS mount and apparently systemd-tmpfiles in 228 changed /usr/lib/tmpfiles.d/home.conf to Q from v.
I will close the bug.
https://github.com/systemd/systemd/issues/1959