Arch Linux

etakeh32

Member

From: Pridnestrovie

Registered: 2014-03-08

Posts: 66

[SOLVED] Failed to start Create Volatile Files and Directories.

Recently I started receiving this error during boot:

systemd[1]: Failed to start Create Volatile Files and Directories.

More info:

[tkh@tk6410 ~]$ sudo 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: disabled)
   Active: failed (Result: exit-code) since Sun 2015-04-19 20:59:29 EDT; 6min ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 442 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 442 (code=exited, status=1/FAILURE)

Apr 19 20:59:29 tk6410 systemd[1]: Starting Create Volatile Files and Directories...
Apr 19 20:59:29 tk6410 systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Apr 19 20:59:29 tk6410 systemd[1]: Failed to start Create Volatile Files and Directories.
Apr 19 20:59:29 tk6410 systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Apr 19 20:59:29 tk6410 systemd[1]: systemd-tmpfiles-setup.service failed.

Although everything still runs, it seems serious so I hope you guys can point me in the right direction. Thanks in advance!

Last edited by etakeh32 (2015-04-21 09:54:51)

etakeh32

Member

From: Pridnestrovie

Registered: 2014-03-08

Posts: 66

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

Solved by removing /var/log/journal folder. (you should mv it to journal.bak to be safe)

foutrelis

Developer

From: Athens, Greece

Registered: 2008-07-28

Posts: 705

Website

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

Removing the /var/log/journal masks the issue by making journald store journal data only in memory (under /run/log/journal).

The correct fix is to enable ACL support in your filesystem:

https://wiki.archlinux.org/index.php/Sy … rt_at_boot

pezz

Member

From: Geelong, Australia

Registered: 2010-05-23

Posts: 83

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

F!#$... Man it'd be nice to be told about these things in a post install message or something.

Thanks, but this has been doing my head in.

amish

Member

Registered: 2014-05-10

Posts: 475

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

Ok I DO NOT have this issue but I thought I should have!

So just wanted to make sure what is going on.

I have ext4 partition.

tune2fs -l /dev/sda3 | grep -i acl
<EMPTY>

i.e. no option containing word acl

Default mount options is (none)

cat /etc/fstab|grep -i acl
<EMPTY>

i.e. acl is NOT mentioned in /etc/fstab as well.

cat /proc/mounts |grep -i acl
<EMPTY>

i.e. acl is NOT there on existing mounts

But when I do:
chacl -l /var/log/journal/XXXXXX8d899XXXXX
/var/log/journal/XXXXXX8d899XXXXX [u::rwx,g::r-x,g:adm:r-x,g:wheel:r-x,m::r-x,o::r-x/u::rwx,g::r-x,g:adm:r-x,g:wheel:r-x,m::r-x,o::r-x]

How did acl work?

Is it that ext4 now has inbuilt acl so it does not show anywhere? Not even in Default mount options?

etakeh32

Member

From: Pridnestrovie

Registered: 2014-03-08

Posts: 66

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

@foutrelis - SPOT ON, thank you!

I set acl option in fstab for my reiserfs system and moved journal.bak back to journal, and the error is gone. It is very odd that in over a year using this setup I never got that error before.

@amish - Not sure why your grep won't return acl, but did read here that ext3, ext4 and btrfs don't require the flag in fstab as they use acl by default.

amish

Member

Registered: 2014-05-10

Posts: 475

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

@etaken32

In your link it infact says that it is required to enable by putting acl in fstab

Even Ubuntu help says same here:
https://help.ubuntu.com/community/FilePermissionsACLs

It says its enabled by default and example is given to know how to detect that its enabled by default.

What is strange that - if it is enabled by default - then in my case why is "Default Mount options" showing (none)??

Again I repeat - I do not have issue but I just want to confirm why ACL is not shown to be enabled and yet it is working!

Last edited by amish (2015-04-22 11:09:01)

etakeh32

Member

From: Pridnestrovie

Registered: 2014-03-08

Posts: 66

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

Sorry, wrong link. There is a possibility that the acl option is already active as default mount option on the filesystem. Btrfs does and possibly ext filesystems do too.

etakeh32

Member

From: Pridnestrovie

Registered: 2014-03-08

Posts: 66

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

So I checked on my EXT4:

[tkh@tk6410 ~]$ tune2fs -l /dev/mapper/vgroup-root | grep acl
Default mount options:    user_xattr acl

My fstab does not have acl flag for that partition.

Although, like I said, I ran reiserfs, where my /var resides, without acl for over a year and just recently got this error.

amish

Member

Registered: 2014-05-10

Posts: 475

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

See thats what I wonder. You are getting acl in "Default mount options".

I do not get it and yet acl seems to be working. Strange.

etakeh32

Member

From: Pridnestrovie

Registered: 2014-03-08

Posts: 66

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

Have you tried to see what happens if you do in fact enable it in fstab? Are you running custom or older kernel?

amish

Member

Registered: 2014-05-10

Posts: 475

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

I am not running very old kernel but yes 3.17.6-1.

New kernels cause fan issues so I can not use them till kernel with patch arrives.

FlowIt

Member

Registered: 2014-10-25

Posts: 243

Re: [SOLVED] Failed to start Create Volatile Files and Directories.

The proposed fix does not work for me. Acl support is enabled for sda1 where /var/log/journal resides (ext4) but I still get the failure message at boot.
These are the permissions: Is there anything wrong with them?

drwxr-sr-x 3 root systemd-journal    4096 Jun 14 13:14 journal