Closed RomuloPBenedetti closed 6 years ago
I expect this to be actually zlib — it's very easy to set compression mode wrong, btrfs provides too many ways to set it. Could you check for example:
btrfs prop get /some/file compression
? — it'd check just one of things that override global mount options. So does chattr +c
.
If you have a directory that you're certain has no compression prop, you can copy in a test file that's 1. compressible, 2. long enough, 3. in a way that won't reflink it (cp
may do so, safer to use cat
or tar
); it should get compressed with the mount's default.
Thanks I was completely unaware that the compression property could get more priority than mount options. The device folder mnt/HDDs
that was in another BTRFS partition had zlib as compression property.
So all is ok then...? Compsize reports the state, documentation about how to set it is probably out of scope here. Not sure where it should go, as the setting order is currently only tribal knowledge among btrfs developers.
Please reopen if there's anything you'd like added to compsize itself.
I've moved a folder from another partition to the current one, mounted with
compress-force=zstd
, to my surprise, with compsize I get:The partition was empty before, I expected it to be forcible compressed to zstd, as it came from another file system.