[WORKAROUNDED] Failed "Create Volatile Files and Directories"

Mons1990 · 2016-02-03 08:54:21

Good morning. Since yesterday I started receiving an error message during boot that complains:

feb 03 09:47:43 arch-desktop systemd[1]: Started Flush Journal to Persistent Storage.
feb 03 09:47:43 arch-desktop systemd[1]: Starting Create Volatile Files and Directories...
feb 03 09:47:43 arch-desktop systemd-tmpfiles[440]: ACL operation on "/var/log/journal/0c0fdd5aa408490da6051788161d4e51" failed:
feb 03 09:47:43 arch-desktop systemd-tmpfiles[440]: ACL operation on "/var/log/journal/0c0fdd5aa408490da6051788161d4e51" failed:
feb 03 09:47:43 arch-desktop systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
feb 03 09:47:43 arch-desktop systemd[1]: Failed to start Create Volatile Files and Directories.
feb 03 09:47:43 arch-desktop systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
feb 03 09:47:43 arch-desktop systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.

Systemctl tells:

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since mer 2016-02-03 09:47:43 CET; 36s ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 440 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
 Main PID: 440 (code=exited, status=1/FAILURE)

feb 03 09:47:43 arch-desktop systemd[1]: Starting Create Volatile Files and Directories...
feb 03 09:47:43 arch-desktop systemd-tmpfiles[440]: ACL operation on "/var/log/journal/0c0fdd5aa408490da6051788161d4e51" failed: Invalid argument
feb 03 09:47:43 arch-desktop systemd-tmpfiles[440]: ACL operation on "/var/log/journal/0c0fdd5aa408490da6051788161d4e51" failed: Invalid argument
feb 03 09:47:43 arch-desktop systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
feb 03 09:47:43 arch-desktop systemd[1]: Failed to start Create Volatile Files and Directories.
feb 03 09:47:43 arch-desktop systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
feb 03 09:47:43 arch-desktop systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.

I have /var in a separate partition formatted in ReiserFS and mounted with

# /dev/sdb1 (var)
UUID=bbe6b555-7af5-44d1-8dc9-88352c76580b          /var          reiserfs          rw,noatime,acl          0 2

Thank you in advance for the help

Last edited by Mons1990 (2016-02-14 21:50:13)

x33a · 2016-02-03 09:25:07

Check if /var is actually mounted with acl enabled.

Also, what's the output of

ls -ld /var/log/journal

Moving to "System Administration".

patroclo7 · 2016-02-03 14:34:09

Look here:

https://bbs.archlinux.org/viewtopic.php … 8#p1599558

If ACL is broken on reiserfs and reiserfs is not developed anymore, then perhaps it is not possible to use reiserfs for /var (but reiserfs on /var makes pacman superfast, thus it is a pity...).

Last edited by patroclo7 (2016-02-03 14:35:26)

patroclo7 · 2016-02-03 14:39:59

A temporary fix is to copy /usr/lib/tmpfiles.d/systemd.conf in /etc/tmpfiles.d/systemd.conf and comment out the following two lines:

a+ /var/log/journal/%m - - - - d:group:adm:r-x,d:group:wheel:r-x
a+ /var/log/journal/%m - - - - group:adm:r-x,group:wheel:r-x

Last edited by patroclo7 (2016-02-03 14:43:35)

Mons1990 · 2016-02-03 18:57:00

x33a wrote:

Check if /var is actually mounted with acl enabled.

Yes, it's specified in fstab, so at least it should be.

x33a wrote:

Also, what's the output of
ls -ld /var/log/journal

$ ls -ld /var/log/journal
drwxr-sr-x 4 root systemd-journal 120 23 apr  2015 /var/log/journal

patroclo7 wrote:

Look here:
https://bbs.archlinux.org/viewtopic.php … 8#p1599558
If ACL is broken on reiserfs and reiserfs is not developed anymore, then perhaps it is not possible to use reiserfs for /var (but reiserfs on /var makes pacman superfast, thus it is a pity...).

This thread has some months, till some days ago it worked flawlessly for me. The only solution I have according to this is to format /var in ext4?

patroclo7 wrote:

A temporary fix is to copy /usr/lib/tmpfiles.d/systemd.conf in /etc/tmpfiles.d/systemd.conf and comment out the following two lines:
a+ /var/log/journal/%m - - - - d:group:adm:r-x,d:group:wheel:r-x
a+ /var/log/journal/%m - - - - group:adm:r-x,group:wheel:r-x

Exactly what does this procedure do?

Thank you all for the answer.

Last edited by Mons1990 (2016-02-03 18:57:47)

x33a · 2016-02-04 05:20:36

Mons1990 wrote:

x33a wrote:
Check if /var is actually mounted with acl enabled.
Yes, it's specified in fstab, so at least it should be.

It's always better not to assume. What's the output of findmnt?

$ ls -ld /var/log/journal
drwxr-sr-x 4 root systemd-journal 120 23 apr  2015 /var/log/journal

I don't see a + at the end of the permissions. That means ACL is not set on that directory.

Here's my output for reference:

drwxr-sr-x+ 1 root systemd-journal 76 Jun  1  2015 /var/log/journal/

Mons1990 · 2016-02-04 16:44:51

x33a wrote:

What's the output of findmnt?

$ findmnt
TARGET                               SOURCE     FSTYPE      OPTIONS
/                                    /dev/sda2  ext4        rw,noatime,discard,data=ordered
├─/proc                              proc       proc        rw,nosuid,nodev,noexec,relatime
│ └─/proc/sys/fs/binfmt_misc         systemd-1  autofs      rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct
├─/sys                               sys        sysfs       rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/security             securityfs securityfs  rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup                   tmpfs      tmpfs       ro,nosuid,nodev,noexec,mode=755
│ │ ├─/sys/fs/cgroup/systemd         cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd
│ │ ├─/sys/fs/cgroup/blkio           cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,blkio
│ │ ├─/sys/fs/cgroup/net_cls         cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,net_cls
│ │ ├─/sys/fs/cgroup/pids            cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,pids
│ │ ├─/sys/fs/cgroup/devices         cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,devices
│ │ ├─/sys/fs/cgroup/memory          cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,memory
│ │ ├─/sys/fs/cgroup/freezer         cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,freezer
│ │ ├─/sys/fs/cgroup/cpu,cpuacct     cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,cpu,cpuacct
│ │ └─/sys/fs/cgroup/cpuset          cgroup     cgroup      rw,nosuid,nodev,noexec,relatime,cpuset
│ ├─/sys/fs/pstore                   pstore     pstore      rw,nosuid,nodev,noexec,relatime
│ ├─/sys/firmware/efi/efivars        efivarfs   efivarfs    rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/debug                debugfs    debugfs     rw,relatime
│ ├─/sys/kernel/config               configfs   configfs    rw,relatime
│ └─/sys/fs/fuse/connections         fusectl    fusectl     rw,relatime
├─/dev                               dev        devtmpfs    rw,nosuid,relatime,size=4049632k,nr_inodes=1012408,mode=755
│ ├─/dev/shm                         tmpfs      tmpfs       rw,nosuid,nodev
│ ├─/dev/pts                         devpts     devpts      rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
│ ├─/dev/hugepages                   hugetlbfs  hugetlbfs   rw,relatime
│ └─/dev/mqueue                      mqueue     mqueue      rw,relatime
├─/run                               run        tmpfs       rw,nosuid,nodev,relatime,mode=755
│ ├─/run/user/120                    tmpfs      tmpfs       rw,nosuid,nodev,relatime,size=810524k,mode=700,uid=120,gid=120
│ │ └─/run/user/120/gvfs             gvfsd-fuse fuse.gvfsd- rw,nosuid,nodev,relatime,user_id=120,group_id=120
│ └─/run/user/1000                   tmpfs      tmpfs       rw,nosuid,nodev,relatime,size=810524k,mode=700,uid=1000,gid=100
│   └─/run/user/1000/gvfs            gvfsd-fuse fuse.gvfsd- rw,nosuid,nodev,relatime,user_id=1000,group_id=100
├─/home                              systemd-1  autofs      rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct
│ └─/home                            /dev/sdb3  ext4        rw,noatime,data=ordered
│   └─/home/mons/.virtualbox/Windows systemd-1  autofs      rw,relatime,fd=39,pgrp=1,timeout=0,minproto=5,maxproto=5,direct
├─/tmp                               tmpfs      tmpfs       rw,nosuid,nodev,relatime,size=4194304k
├─/scratch                           tmpfs      tmpfs       rw,nosuid,nodev,relatime
├─/boot                              /dev/sda1  vfat        rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,sh
└─/var                               /dev/sdb1  reiserfs    rw,noatime,acl

x33a · 2016-02-05 04:52:01

OK, so acl is set for the mount option, but the directory itself doesn't have acl set. Try moving the journal directory to journal.bak or something and run

# systemctl restart systemd-journald

That should recreate the directory. Then see if the new directory has acl set or not.

tangram · 2016-02-06 18:12:52

Hi everyone.
I got same error.
I would like to change filesystem type on my /var partition from reiserfs to ext4. How can I do that ?
Thank you for the help.

x33a · 2016-02-07 09:55:14

@tangram, converting should be fairly easy. Here's a link for your reference. https://bbs.archlinux.org/viewtopic.php?id=170819

If you have any further questions, please open a new thread so as not to derail this one.

tangram · 2016-02-07 17:19:21

@x33a thank you, it's exactly what I need.
Do you think it could be a good idea to tweak some fs creation parmeteres for better performance with small files,
for exmp. like described in /etc/mke2fs.conf, compare defaults and small section ?.

tangram · 2016-02-07 17:28:43

@x33a, sorry I missed the last sentence "If you have any further questions ..."

Mons1990 · 2016-02-10 17:37:22

x33a wrote:

OK, so acl is set for the mount option, but the directory itself doesn't have acl set. Try moving the journal directory to journal.bak or something and run
# systemctl restart systemd-journald
That should recreate the directory. Then see if the new directory has acl set or not.

It doesn't.

x33a · 2016-02-11 05:04:42

It doesn't recreate the directory?

Try setting

Storage=persistent

in journald.conf.

Then it should be created.

Mons1990 · 2016-02-14 14:19:33

x33a wrote:

It doesn't recreate the directory?
Try setting
Storage=persistent
in journald.conf.
Then it should be created.

It works but no + at the end of permissions

# mv /var/log/journal /var/log/journal.bak
# systemctl restart systemd-journald
$ cd /var/log
$ ls
btmp    faillog  journal      lastlog  pacman.log  speech-dispatcher  wtmp.1      Xorg.0.log.old  Xorg.1.log.old
btmp.1  gdm      journal.bak  old      samba       wtmp               Xorg.0.log  Xorg.1.log
$ ls -ld /var/log/journal
drwxr-xr-x 3 root root 96 14 feb 15.14 /var/log/journal

Mons1990 · 2016-02-14 21:50:48

Finally I formatted the whole /var partition in ext4. Thank you very much anyway for the help.

Arch Linux

#1 2016-02-03 08:54:21

[WORKAROUNDED] Failed "Create Volatile Files and Directories"

#2 2016-02-03 09:25:07

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#3 2016-02-03 14:34:09

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#4 2016-02-03 14:39:59

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#5 2016-02-03 18:57:00

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#6 2016-02-04 05:20:36

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#7 2016-02-04 16:44:51

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#8 2016-02-05 04:52:01

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#9 2016-02-06 18:12:52

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#10 2016-02-07 09:55:14

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#11 2016-02-07 17:19:21

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#12 2016-02-07 17:28:43

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#13 2016-02-10 17:37:22

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#14 2016-02-11 05:04:42

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#15 2016-02-14 14:19:33

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

#16 2016-02-14 21:50:48

Re: [WORKAROUNDED] Failed "Create Volatile Files and Directories"

Board footer