public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: btrfs raid 5/6
Date: Thu, 7 Dec 2017 23:35:45 +0100	[thread overview]
Message-ID: <20171207223545.GC18433@tp> (raw)
In-Reply-To: <5A29B769.7030400@youngman.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

On Thu, Dec 07, 2017 at 09:49:29PM +0000, Wols Lists wrote:

> > So in case I ever need to send in a drive for repair/replacement, noone can
> > read from it (or only in tiny bits'n'pieces from a hexdump), because each
> > disk contains a mix of data and parity blocks.
> >
> > I think I'm finally sold. :)
> > And with that, good night.
>
> So you've never heard of LUKS?

Sure thing, my laptop’s whole SSD is LUKSed and so are all my other home and
backup partitions. But encrypting ZFS is different, because every disk needs
to be encrypted separately since there is no separation between the FS and
the underlying block device.

This will result in a big computational overhead, choking my poor Celeron.
When I benchmarked reading from a single LUKS container in a ramdisk, it
managed around 160 MB/s IIRC. I might give it a try over the weekend before
I migrate my data, but I’m not expecting miracles. Should have bought an i3
for that.

> (Oh - and md raid-5/6 also mix data and parity, so the same holds true
> there.)

Ok, wasn’t aware of that. I thought I read in a ZFS article that this were a
special thing.

-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

This is no signature.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-07 22:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 22:30 [gentoo-user] OT: btrfs raid 5/6 Bill Kenworthy
2017-12-01 15:59 ` J. Roeleveld
2017-12-01 16:58 ` Wols Lists
2017-12-01 17:14   ` Rich Freeman
2017-12-01 17:24     ` Wols Lists
2017-12-06 23:28     ` Frank Steinmetzger
2017-12-06 23:35       ` Rich Freeman
2017-12-07  0:13         ` Frank Steinmetzger
2017-12-07  0:29           ` Rich Freeman
2017-12-07 21:37             ` Frank Steinmetzger
2017-12-07 21:49               ` Wols Lists
2017-12-07 22:35                 ` Frank Steinmetzger [this message]
2017-12-07 23:48                   ` Wols Lists
2017-12-09 16:58                     ` J. Roeleveld
2017-12-09 18:28                       ` Wols Lists
2017-12-09 23:36                         ` Rich Freeman
2017-12-10  9:45                           ` Wols Lists
2017-12-10 15:07                             ` Rich Freeman
2017-12-10 21:00                               ` Wols Lists
2017-12-11  1:33                                 ` Rich Freeman
2017-12-11 23:20                 ` Frank Steinmetzger
2017-12-12 10:15                   ` Neil Bothwick
2017-12-12 12:18                     ` Wols Lists
2017-12-12 13:24                       ` Neil Bothwick
2017-12-07  7:54         ` Richard Bradfield
2017-12-07  9:28           ` Frank Steinmetzger
2017-12-07  9:52             ` Richard Bradfield
2017-12-07 14:53               ` Frank Steinmetzger
2017-12-07 15:26                 ` Rich Freeman
2017-12-07 16:04                   ` Frank Steinmetzger
2017-12-07 23:09                     ` Rich Freeman
2017-12-07 20:02                 ` Wols Lists
2017-12-07 18:35               ` Wols Lists
2017-12-07 20:17                 ` Richard Bradfield
2017-12-07 20:39                   ` Wols Lists

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=20171207223545.GC18433@tp \
    --to=warp_7@gmx.de \
    --cc=gentoo-user@lists.gentoo.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