linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: "Konstantin V. Gavrilenko" <k.gavrilenko@arhont.com>
Cc: Linux fs Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs subvolume mount with different options
Date: Sat, 13 Jan 2018 01:37:49 +0500	[thread overview]
Message-ID: <20180113013749.5338c057@natsu> (raw)
In-Reply-To: <20055256.49.1515779377187.JavaMail.gkos@dynomob>

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

  parent reply	other threads:[~2018-01-12 20:37 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 [this message]
2018-01-15 13:57   ` Konstantin V. Gavrilenko

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=20180113013749.5338c057@natsu \
    --to=rm@romanrm.net \
    --cc=k.gavrilenko@arhont.com \
    --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).