From: "Konstantin V. Gavrilenko" <k.gavrilenko@arhont.com>
To: Linux fs Btrfs <linux-btrfs@vger.kernel.org>
Cc: Roman Mamedov <rm@romanrm.net>
Subject: Re: btrfs subvolume mount with different options
Date: Mon, 15 Jan 2018 13:57:23 +0000 (GMT) [thread overview]
Message-ID: <6077373.226.1516024638372.JavaMail.gkos@dynomob> (raw)
In-Reply-To: <20180113013749.5338c057@natsu>
Thanks, chattr +C is that's what I am currently using.
Also you already answered my next question, why it is not possible to set +C attribute on the existing file :)
Yours sincerely,
Konstantin V. Gavrilenko
----- Original Message -----
From: "Roman Mamedov" <rm@romanrm.net>
To: "Konstantin V. Gavrilenko" <k.gavrilenko@arhont.com>
Cc: "Linux fs Btrfs" <linux-btrfs@vger.kernel.org>
Sent: Friday, 12 January, 2018 9:37:49 PM
Subject: Re: btrfs subvolume mount with different options
On Fri, 12 Jan 2018 17:49:38 +0000 (GMT)
"Konstantin V. Gavrilenko" <k.gavrilenko@arhont.com> wrote:
> Hi list,
>
> just wondering whether it is possible to mount two subvolumes with different mount options, i.e.
>
> |
> |- /a defaults,compress-force=lza
You can have use different compression algorithms across the filesystem
(including none), via "btrfs properties" on directories or subvolumes. They
are inherited down the tree.
$ mkdir test
$ sudo btrfs prop set test compression zstd
$ echo abc > test/def
$ sudo btrfs prop get test/def compression
compression=zstd
But it appears this doesn't provide a way to apply compress-force.
> |- /b defaults,nodatacow
Nodatacow can be applied to any dir/subvolume recursively, or any file (as long as it's created but not
written yet) via chattr +C.
--
With respect,
Roman
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-01-15 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 17:49 btrfs subvolume mount with different options Konstantin V. Gavrilenko
2018-01-12 20:27 ` Timofey Titovets
2018-01-12 20:37 ` Roman Mamedov
2018-01-15 13:57 ` Konstantin V. Gavrilenko [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=6077373.226.1516024638372.JavaMail.gkos@dynomob \
--to=k.gavrilenko@arhont.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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).