From: Karl-Philipp Richter <richter@richtercloud.de>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Explain the precedence of btrfs properties over mount options
Date: Sun, 08 Mar 2015 16:34:20 +0100 [thread overview]
Message-ID: <54FC6BFC.8090505@richtercloud.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
Hi,
The manpage of `btrfs property` would be a good place to explain the
precedence of properties over mount options, e.g. what happens when the
mount option `compress` is set to `zlib` and the property for same
subvolume is set to `""` (indicating no compression as you know)? What
happens when `compress-force` mount option is specified which doesn't
have an equivalent in properties?
Best regards,
Kalle
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-03-08 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54FC6BFC.8090505@richtercloud.de \
--to=richter@richtercloud.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.