linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Ryczkowski <adam.ryczkowski@statystyka.net>
To: linux-btrfs@vger.kernel.org
Subject: Can btrfs handle different RAID levels for different subvolumes?
Date: Sun, 14 Jul 2013 16:50:35 +0200	[thread overview]
Message-ID: <51E2BABB.3060506@statystyka.net> (raw)

Can one btrfs filesystem handle different RAID levels e.g. for different 
subvolumes? If so, how does deduplication with bedup 
(https://github.com/g2p/bedup) across them work?

(It has been asked already on the Net 
(http://unix.stackexchange.com/questions/82869/can-btrfs-handle-different-raid-levels-for-different-subvolumes) 
but the question didn't get the answer. I guess answering it should be 
straightforward for you, guys :-) )

Adam Ryczkowski



             reply	other threads:[~2013-07-14 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-14 14:50 Adam Ryczkowski [this message]
2013-07-14 15:14 ` Can btrfs handle different RAID levels for different subvolumes? Hugo Mills

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=51E2BABB.3060506@statystyka.net \
    --to=adam.ryczkowski@statystyka.net \
    --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).