From: cwillu <cwillu@cwillu.com>
To: merc1984@f-m.fm
Cc: Mitch Harder <mitch.harder@sabayonlinux.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Encryption
Date: Wed, 12 Dec 2012 14:22:07 -0600 [thread overview]
Message-ID: <CAE5mzviPrx5s9c2rP=qd36pBbNX5MdzwKmsf3khkvRk3jtaCyg@mail.gmail.com> (raw)
In-Reply-To: <1355342784.940.140661165251717.298B576B@webmail.messagingengine.com>
On Wed, Dec 12, 2012 at 2:06 PM, <merc1984@f-m.fm> wrote:
> On Wed, Dec 12, 2012, at 10:48, cwillu wrote:
>> Sayeth the FAQ:
>
> Oh pardon me, it's BTRFS RAID that's a no-go, which is just as critical
> to me as I have a 4 disk 8TB array.
> The FAQ goeth on to Say:
> -----------------------------------------------------------
> This pretty much forbids you to use btrfs' cool RAID features if you
> need encryption. Using a RAID implementation on top of several encrypted
> disks is much slower than using encryption on top of a RAID device. So
> the RAID implementation must be on a lower layer than the encryption,
> which is not possible using btrfs' RAID support.
> -----------------------------------------------------------
>
> You saw that I need RAID above. Were you just trying to criticize my
> memory of the FAQ cwillu?
It's not asking for trouble, it's just asking for poor performance,
and I suspect even that will depend greatly on the workload.
Snapshots still have nothing to do with it: you could have btrfs
(with snapshots) on dm-crypt on mdraid. Btrfs would just lose the
ability to try alternate mirrors and similar; snapshots would still
work just fine.
next prev parent reply other threads:[~2012-12-12 20:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 16:16 merc1984
2012-12-12 17:12 ` Encryption merc1984
2012-12-12 18:31 ` Encryption Mitch Harder
2012-12-12 18:38 ` Encryption merc1984
2012-12-12 18:48 ` Encryption cwillu
2012-12-12 20:06 ` Encryption merc1984
2012-12-12 20:22 ` cwillu [this message]
2012-12-13 9:17 ` Encryption Sander
2012-12-13 17:23 ` Encryption merc1984
2012-12-13 22:39 ` Encryption Hugo Mills
-- strict thread matches above, loose matches on Subject: below --
2015-02-16 17:19 encryption Henry Noack
2015-02-18 11:03 ` encryption Stefan Hajnoczi
2015-02-18 11:58 ` encryption Markus Armbruster
2011-01-20 15:05 Encryption Carl Cook
2011-01-20 15:14 ` Encryption Hugo Mills
2011-01-20 16:10 ` Encryption Josef Bacik
2003-03-22 23:22 Encryption Pierre Abbat
2003-03-22 23:29 ` Encryption Yury Umanets
2003-03-24 20:37 ` Encryption Hans Reiser
2003-03-25 19:18 ` Encryption Edward Shushkin
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='CAE5mzviPrx5s9c2rP=qd36pBbNX5MdzwKmsf3khkvRk3jtaCyg@mail.gmail.com' \
--to=cwillu@cwillu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=merc1984@f-m.fm \
--cc=mitch.harder@sabayonlinux.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.