Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[opentmpfiles-setup] chattr three error messages #2
*� Setting up tmpfiles.d entries ...
kernel 4.10.1 , systemd 232, openrc 0.24, opentmpfiles 0.1.3
The error is caused by the systemd config file
Of course, the nocow attribute cannot be set on many filesystems where it makes not sense (like ext2), and systemd gracefully ignores the corresponding "error" (which is more an informal message).
It is really annoying that opentmpfiles-setup fails to start because of such an informal message, thus preventing all dependent services to start properly, too.
A workaround is to generate a 0-byte file
Anyway, it would be nicer if opentmpfiles could handle this automatically without requiring such hacks (which have to be remembered to be removed when the underlying file system changes.)
The config file with the problem is /usr/lib/tmpfiles.d/journal-nocow.conf .
I do think tmpfiles.d design is the problem here by allowing settings -that only work under certain conditions- to fail silently.
It depends from case to case. For 'h' and 'H' the function path_set_attribute() of src/tmpfiles/tmpfiles.c is called (in case of H recursively).
This function returns with an error only if the file does not exist or is of a bad type.
You commented out the only 3 non-comment lines of that file. So effectively you generated a 0-byte file.