systemd: Create Volatile Files and Directories failed (probably related to ACL)

English Install/Boot/Login
1

Hi,
i noticed that during boot systemd posts that a unit failed to start, at this point i cannot really see what unit it is as the booting is so fast (but the error message is clearly similar to the topic of this thread). But i do not notice any problems with the system related to this after boot. Btw. the system is a pretty new notebook and i just installed tumbleweed yesterday.

After boot i checked:

systemctl --failed

and get one failed unit:

UNIT___________________________LOAD___ACTIVE_SUB______DESCRIPTION________
systemd-tmpfiles-setup.service loaded failed failed   Create Volatile Files and Directories

I tried to find the solution by myself but only found some references to the Arch Linux wiki, stating that the problem is due to ACL not activated for the partition which contains /var/journal (or /var/log/journal i am not sure about this). But i also found that btrfs does not need to have this enabled because it is enabled by default.
Anyway my system has two physical hard discs:
/dev/sda (a normal hard disc which contains one XFS partition for /home)
/dev/sdb (a SSD hard disc which contains the EFI fat partition, a swap partition and a BTRFS partition for / including all of the subvolumes [which includes /var])

So it is clear that the relevant partition is a btrfs one. But i was not able to solve my problem with that information, can anyone help me with this?

2

Regarding this specific problem about creating volatile files, there is a current/recent thread

https://forums.opensuse.org/showthread.php/525596-systemd-tmpfiles-setup-service-Create-Volatile-Files-and-Directories?highlight=volatile

TSU

3

Thanks but it seems that the thread has not much to offer. Can at least someone confirm that the problem is not critical? is this something i can ignore until it gets fixed (if it is a systemd problem).

4

What “systemctl status systemd-tmpfiles-setup.service” says?

5

I do not know what happened, maybe it was the yesterdays update, but as i just booted my notebook the problem was gone.(but maybe it is just a coincidence and the problem is back after the next boot).
Anyway this is the systemd unit status:


user:~> systemctl status systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disable
   Active: active (exited) since Sat 2017-07-08 09:32:39 CEST; 4min 3s ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 1022 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=
 Main PID: 1022 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/systemd-tmpfiles-setup.service

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.