From: "Chris Murphy" <lists@colorremedies.com>
To: "Zygo Blaxell" <ce3g8jdj@umail.furryterror.org>,
"Nemcev Aleksey" <Nemcev_Aleksey@inbox.ru>
Cc: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: compsize reports that filesystem uses zlib compression, while I set zstd compression everywhere
Date: Thu, 27 Oct 2022 09:21:53 -0400 [thread overview]
Message-ID: <0f6f1ecb-84d4-4fac-9fcc-5932d5b4f73d@app.fastmail.com> (raw)
In-Reply-To: <Y1nY2FJGYS+iWMcS@hungrycats.org>
On Wed, Oct 26, 2022, at 9:03 PM, Zygo Blaxell wrote:
>> And also it's not possible to specify compression level in defragment - so,
>> I'll change the level in subvolume properties, defragment with -czstd, and
>> change the level back.
>
> It's not possible to set the level in subvol properties either. Only the
> compress= mount option can set the level.
$ sudo btrfs property set test compression zstd:1
$ sudo btrfs property get test
compression=zstd:1
$ sudo btrfs property set test compression zstd:f
$ sudo btrfs property get test
compression=zstd:f
It's allowing the arbitrary setting of compression values. This is with btrfs-progs 6.0. Progs is being too permissive, it shouldn't silently set invalid values. But then even with valid values, I'm pretty sure right now the kernel ignores the compression properties.
--
Chris Murphy
next prev parent reply other threads:[~2022-10-27 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 10:21 compsize reports that filesystem uses zlib compression, while I set zstd compression everywhere Nemcev Aleksey
2022-10-26 19:07 ` Chris Murphy
2022-10-26 22:29 ` Nemcev Aleksey
2022-10-27 1:03 ` Zygo Blaxell
2022-10-27 13:21 ` Chris Murphy [this message]
2022-10-27 14:32 ` Zygo Blaxell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f6f1ecb-84d4-4fac-9fcc-5932d5b4f73d@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=Nemcev_Aleksey@inbox.ru \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox