Skip to content

systemd[1]: Failed to start Create Volatile Files and Directories. - on Arch Linux having zfsonlinux as root

I just got the following entry on my boot up today:

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

After a while of searching using my favorit searchengine, I (as usual ;-)) found the most fitting solution in the bbs.archlinux.org.
The solution is given in the manpage of the tmpfiles.d.
tmpfiles.d(5) wrote:

If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in /etc/tmpfiles.d/ bearing the same filename.

So all you have to do is:

sudo su

cd /usr/lib/tmpfiles.d

cp journal-nocow.conf journal-nocow.conf.bak

rm journal-nocow.conf.bak

ln -s /dev/null journal-nocow.conf


And thats it. Fingers crossed you system will boot without errors.

Translate to de es fr it pt ja

zfs as root with luks on arch linux and the small trouble after upgrading the kernel

Everytime the kernel gets updated, my system only reaches the busybox afterwards.
Currently, I have no idea why this happens exactly. But at least, I know how to handle it.
The zfs module is loaded, so all you need to do is to execute

zpool import -f 
, followed by an
zpool export 
.
It looks like there is a problem with exporting the pool while rebooting, or maybe an error while importing. It is marked as "not exported correctly", that is why booting fails. After the two commands from above, you can enter
reboot
and everything should be fine again.

Translate to de es fr it pt ja

howto fix bootup error message "Failed to start Create Volatile Files and Directories." from "systemd-tmpfiles-setup.service"

Give is, that you get an error message while booting up your system from "systemd-tmpfiles-setup.service" with the description "Failed to start Create Volatile Files and Directories.".
By using systemctl with systemctl status systemd-tmpfiles-setup.service, you get the same description.
A quick look into the archlinux wiki offers you the solution named enable acl in your file system.
If you are running zfs as your root, you have to execute zfs set acltype=posixacl #your_pool_name. To validate if it is working, execute zfs get acltype before and after the set.

If you want to know more, you can read the following links:

Translate to de es fr it pt ja

web - zfsonlinux 0.6.4. released - zfs-announce mailing list

The Linux team is happy to announce a new release of OpenZFS on Linux. The 0.6 4 release adds support for 6 new feature flags, multiple new properties, asynchronous IO, support for Linux kernels up to 4.0 and more.
NEW FUNCTIONALITY
* Compatible with kernels up to Linux 4.0.
* New feature flags (additional details below):
- spacemap_histogram
- extensible_dataset
- bookmarks
- enabled_txg
- hole_birth
- embedded_data
* New asynchronous I/O (AIO) support.
* New fallocate() FALLOC_FL_PUNCH_HOLE support.
* New fragmentation metric in 'zpool list'.
* New LZ4 compression of meta data.
* New "redundant_metadata" property controls desired redundancy level.
* New "overlay" property controls behavior for non-empty mount points.
* New 'zpool list -v' shows individual disk capacity.
* New 'zpool get -H' (scripted mode) support.
* New 'zpool create -t' creates a pool with a temporary name.
* New arc_summary.py script from FreeNAS.
* New bash completion support.
* New DTRACE_PROBES integrated with Linux tracepoints.
* New compressed block histograms with zdb.
* New verbatim pool imports with zdb.

What a release, thank you very much for the work and the damn long list of new features, improvements and bug fixes!

Translate to de es fr it pt ja