You are not logged in.
Today the upgrade of "systemd", "systemd-libs" and "systemd-sysvcompat" (250.1-1) shows me these errors:
....
( 6/14) Creating temporary files...
Cannot set file attributes for '/var/log/journal', maybe due to incompatibility in specified attributes, previous=0x10001000, current=0x10001000, expected=0x10801000, ignoring.
Cannot set file attributes for '/var/log/journal/6f58ecce34924bdcbe0fa6e4ce667fee', maybe due to incompatibility in specified attributes, previous=0x00001000, current=0x00001000, expected=0x00801000, ignoring.
Cannot set file attributes for '/var/log/journal/remote', maybe due to incompatibility in specified attributes, previous=0x10001000, current=0x10001000, expected=0x10801000, ignoring.
Cannot set file attributes for '/var/lib/mysql', maybe due to incompatibility in specified attributes, previous=0x10001000, current=0x10001000, expected=0x10801000, ignoring.
( 7/14) Reloading device manager configuration...
....
Should I check something or can I ignore it?
Last edited by j1simon (2022-01-06 16:42:30)
Offline
The errors are shown at boot too:
ene 06 13:26:54 juan-PC systemd[1]: Starting Create Volatile Files and Directories...
ene 06 13:26:54 juan-PC systemd-tmpfiles[1143]: Cannot set file attributes for '/var/log/journal', maybe due to incompatibility in specified attributes, previous=0x10001000, current=0x10001000, expected=0x10801000, ignoring.
ene 06 13:26:54 juan-PC systemd-tmpfiles[1143]: Cannot set file attributes for '/var/log/journal/6f58ecce34924bdcbe0fa6e4ce667fee', maybe due to incompatibility in specified attributes, previous=0x00001000, current=0x00001000, expected=0x00801000, ignoring.
ene 06 13:26:54 juan-PC systemd-tmpfiles[1143]: Cannot set file attributes for '/var/log/journal/remote', maybe due to incompatibility in specified attributes, previous=0x10001000, current=0x10001000, expected=0x10801000, ignoring.
ene 06 13:26:54 juan-PC systemd-tmpfiles[1143]: Cannot set file attributes for '/var/lib/mysql', maybe due to incompatibility in specified attributes, previous=0x10001000, current=0x10001000, expected=0x10801000, ignoring.
ene 06 13:26:54 juan-PC systemd[1]: Finished Create Volatile Files and Directories.
Offline
0x00800000 is FS_NOCOW_FL - what is not a thing on directories.
Edit except for apparently btrfs - what also seems the only supported FS here. Otherwise you get an error.
Offender is /usr/lib/tmpfiles.d/journal-nocow.conf
Last edited by seth (2022-01-06 16:19:44)
Online
My root filesystem is F2FS (it's a NVMe). So, is it safe delete this file? Or is it better ignore it?
Offline
You could shadow it in /etc/tmpfiles.d (copy and alter it)
Online
You could shadow it in /etc/tmpfiles.d (copy and alter it)
Thanks, I also had to copy/change "/usr/lib/tmpfiles.d/mariadb.conf".
Offline
I thought this had already been addressed in 250.1 by https://github.com/systemd/systemd-stab … 79ecb6d657
Offline
It's separated but still logged, https://github.com/systemd/systemd/blob … es.c#L1339
Online
That would require debug logging to be enabled?
Offline
On a second look, that line seems also to log the actual errno [edit: and uses different wording], so it's probably not the case and "r == -ENOANO" is hit.
Might be F2FS not returning the proper error and seth hits the Sarcophagus ;-)
Last edited by seth (2022-01-06 22:45:39)
Online
Hi, can you explain in more detail what needs to be done?
Offline
The error itself is harmless; systemd tries to set an attribute on a filesystem that doesn't support it.
Online
I am on f2fs filesystem as well and 250.3 of systemd, the issue still exists, I see following output
% systemd-tmpfiles --create --prefix /var/log/journal
Setting access ACL "u::rwx,g::r-x,g:wheel:r-x,g:adm:r-x,m::r-x,o::r-x" on /var/log/journal failed: Operation not permitted
Failed to re-open '/var/log/journal': Operation not permitted
Setting access ACL "u::rwx,g::r-x,g:wheel:r-x,g:adm:r-x,m::r-x,o::r-x" on /var/log/journal/5e3488842ead463ea6a910cd8e28438c failed: Operation not permitted
Failed to re-open '/var/log/journal/5e3488842ead463ea6a910cd8e28438c': Operation not permitted
Failed to re-open '/var/log/journal/remote': Operation not permitted
Setting access ACL "u::rw-,g::r-x,g:wheel:r--,g:adm:r--,m::r--,o::---" on /var/log/journal/5e3488842ead463ea6a910cd8e28438c/system.journal failed: Operation not permitted
Offline
I am on f2fs filesystem as well and 250.3 of systemd, the issue still exists
Have you reported it to the systemd developers? https://github.com/systemd/systemd/issues
Offline
khem wrote:I am on f2fs filesystem as well and 250.3 of systemd, the issue still exists
Have you reported it to the systemd developers? https://github.com/systemd/systemd/issues
For F2FS this issue from systemd seems to be related. - https://github.com/systemd/systemd/issues/26318
and it is a problem in filesystem rather than systemd
Offline
For F2FS this issue from systemd seems to be related. - https://github.com/systemd/systemd/issues/26318
and it is a problem in filesystem rather than systemd
f2fs's behavior is intentional https://lore.kernel.org/linux-f2fs-deve … gmail.com/ please raise with them that systemd expects an error or with systemd that it is intentional.
Edit:
See also https://git.kernel.org/pub/scm/linux/ke … v6.5#n1000 and https://github.com/systemd/systemd/comm … a6198a24a2
Last edited by loqs (2023-08-29 21:28:04)
Offline