New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd-tmpfiles prints weird errors when setting file attributes that conflict #17690
Labels
Comments
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Nov 23, 2020
…multaneously on btrfs files Closes systemd#17690.
Fix is waiting in #17693. |
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Nov 23, 2020
…multaneously on btrfs files Closes systemd#17690.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Nov 24, 2020
…multaneously on btrfs files Closes systemd#17690.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Nov 27, 2020
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Dec 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systemd version the issue has been seen with
Used distribution
Linux kernel version used (
uname -a
)CPU architecture issue was seen on
Expected behaviour you didn't see
Unexpected behaviour you saw
My investigation showed that these errors are only printed when compression was enabled on the directories systemd-tmpfiles tries to set the
+C
attribute on. Runningchattr -c
on the directories listed in the error messages fixed the errors.It seems to me that compression and no CoW cannot be enabled together on btrfs.
Maybe this can be fixed by also disabling compression in master/tmpfiles.d/journal-nocow.conf, if thats possible, sensible and does not hurt on other filesystems?
The other issue here is, maybe the error messages could be improved? It took me some googling to get to the root of the issue...
Steps to reproduce the problem
EDIT: It seems this only happens if the attributes are used via
chattr +c
orbtrfs property set ./dir compression lzo
, but not when using the mount optioncompress=
.Sounds like there could be a btrfs bug at play here, too, but I dont think thats the case since
btrfs(5)
states for thenodatacow
mount option:Nodatacow implies nodatasum, and disables compression.
also, showing that
+c
and+C
seem to conflict:The text was updated successfully, but these errors were encountered: