From: Hugo Mills <hugo@carfax.org.uk>
To: "Christian Völker" <cvoelker@knebb.de>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [Docs]? Only one Subvolume with DUP (or different parameters)?
Date: Tue, 16 Feb 2016 19:46:25 +0000 [thread overview]
Message-ID: <20160216194625.GO30635@carfax.org.uk> (raw)
In-Reply-To: <56C377BB.9020101@knebb.de>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Tue, Feb 16, 2016 at 08:25:47PM +0100, Christian Völker wrote:
> Hi Guys,
>
> sorry for the simple question and I assume every developer here laughs
> about this question.
>
> Anyway:
>
> I have read loads of documents but did not find an answer for sure. Even
> though I assume I am right.
>
> On a btrfs filesystem created; is it possible to have subvolumes with
> data duplication and another subvolume without (resp. with just metadata
> duplication)?
No.
It may happen at some point, but it's not possible right now.
Hugo.
> I have some large filesystems currently with ext4 and I am thinking of
> changing to btrfs. Some of the data is more important than others. So I
> want to have data duplication on the important files (sorted in a mount
> point) and without for the other subvolume.
>
> So I want to have the advantage of redundancy of important files
> combined with the flexibility of the volume manager and shared disk space.
>
> Possible?
>
>
> GReetings
>
> Christian
>
--
Hugo Mills | "I don't like the look of it, I tell you."
hugo@... carfax.org.uk | "Well, stop looking at it, then."
http://carfax.org.uk/ |
PGP: E2AB1DE4 | The Goons
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-02-16 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 19:25 [Docs]? Only one Subvolume with DUP (or different parameters)? Christian Völker
2016-02-16 19:46 ` Hugo Mills [this message]
2016-02-17 4:49 ` Duncan
2016-02-17 12:15 ` 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=20160216194625.GO30635@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=cvoelker@knebb.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 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).