From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Eugene Bright <eugene@bright.gdn>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS support per-subvolume compression, isn't it?
Date: Tue, 28 Aug 2018 07:10:23 -0400 [thread overview]
Message-ID: <6ce9fe54-71ac-4fbe-4423-2a7a1df4087b@gmail.com> (raw)
In-Reply-To: <9433856.DUzOFri1R6@linux.local>
On 2018-08-27 17:05, Eugene Bright wrote:
> Greetings!
>
> BTRFS wiki says there is no per-subvolume compression option [1].
>
> At the same time next command allow me to set properties per-subvolume:
> btrfs property set /volume compression zstd
>
> Corresponding get command shows distinct properties for every subvolume.
> Should wiki be updated?
>
The wiki should be updated, but it's not technically wrong.
What the wiki is talking about is per-subvolume mount options to control
compression (so, mounting individual subvolumes from the same volume
with different `compress=` or `compress-force=` mount options), which is
not currently supported.
You are correct though that properties can be used to achieve a similar
result (compressing differently for different subvolumes.
prev parent reply other threads:[~2018-08-28 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 21:05 BTRFS support per-subvolume compression, isn't it? Eugene Bright
2018-08-28 11:10 ` Austin S. Hemmelgarn [this message]
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=6ce9fe54-71ac-4fbe-4423-2a7a1df4087b@gmail.com \
--to=ahferroin7@gmail.com \
--cc=eugene@bright.gdn \
--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;
as well as URLs for NNTP newsgroup(s).