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.
I run into a lot of trouble when i try to compile and want to run the current state of zfsonlinux. I tried a lot and by spending more time then expected and doing configurations/script adaptations i real don't understand 100 percent, i was able to keep things running. Nevertheless, i am happy that the aur package from zfsonlinux is updated a few hours ago.
While writing, i have finished the building and now my zfs is up and running smoothly :-).
Thanks again to the team of zfsonlinux.org and also to the aur package maintainer demizer (including every member of his team) by providing this easy way of using this great filesystem on linux.
Not perfectly matching but also worth a look, at the EuroBSDcon, there was a session about "tuning ZFS on FreeBSD". It is FreeBSD but take some minutes and take a look at the slides. The more you know about zfs, the more you can handle it (and praise a bit to the r.i.p. company sun of course).