From: Eugene Bright <eugene@bright.gdn>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS support per-subvolume compression, isn't it?
Date: Tue, 28 Aug 2018 00:05:59 +0300 [thread overview]
Message-ID: <9433856.DUzOFri1R6@linux.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
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?
--
King regards
Eugene Bright
IT engineer
--------
[1] https://btrfs.wiki.kernel.org/index.php/Compression#Can_I_set_compression_per-subvolume.3F
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-08-28 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 21:05 Eugene Bright [this message]
2018-08-28 11:10 ` BTRFS support per-subvolume compression, isn't it? Austin S. Hemmelgarn
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=9433856.DUzOFri1R6@linux.local \
--to=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).