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: Tue, 12 Dec 2017 00:20:48 +0100	[thread overview]
Message-ID: <20171211232048.GA18223@tp> (raw)
In-Reply-To: <5A29B769.7030400@youngman.org.uk>

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

On Thu, Dec 07, 2017 at 09:49:29PM +0000, Wols Lists wrote:
> On 07/12/17 21:37, Frank Steinmetzger wrote:
> > Ooooh, I just came up with another good reason for raidz over mirror:
> > I don't encrypt my drives because it doesn't hold sensitive stuff. (AFAIK
> > native ZFS encryption is available in Oracle ZFS, so it might eventually
> > come to the Linux world).
> >
> > 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?
>
> GPT
> LUKS
> MD-RAID
> Filesystem

My new drives are finally here. One of them turned out to be an OEM. -_-
The shop says it will cover any warranty claims and it’s not a backyard
seller either, so methinks I’ll keep it.

To evaluate LUKS, I created the following setup (I just love ASCII-painting
in vim ^^):

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ tmpfs                                                           ┃
┃ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┃
┃ │  1 GB file  │ │  1 GB file  │ │  1 GB file  │ │  1 GB file  │ ┃
┃ └──────┬──────┘ └──────┬──────┘ └──────┬──────┘ └──────┬──────┘ ┃
┃        V               V               V               V        ┃
┃ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┃
┃ │ LUKS device │ │ LUKS device │ │ LUKS device │ │ LUKS device │ ┃
┃ └──────┬──────┘ └──────┬──────┘ └──────┬──────┘ └──────┬──────┘ ┃
┃        V               V               V               V        ┃
┃ ┌─────────────────────────────────────────────────────────────┐ ┃
┃ │                          RaidZ2                             │ ┃
┃ └─────────────────────────────────────────────────────────────┘ ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

While dd'ing a 1500 MB file from and to the pool, my NAS Celeron achieved
(with the given number of vdevs out of all 4 being encrypted):

          non-encrypted    2 encrypted   4 encrypted
────────────────────────────────────────────────────
read          1600 MB/s       465 MB/s      290 MB/s
write         ~600 MB/s      ~200 MB/s     ~135 MB/s
scrub time                                   10 s (~ 100 MB/s)

So performance would be juuuust enough to satisfy GBE. I wonder though how
long a real scrub/resilver would take. The last scrub of my mirror, which
has 3.8 TB allocated, took 9¼ hours. Once the z2 pool is created and the
data migrated, I *will* have to do a resilver in any case, because I only
have four drives and they will all go into the pool, but two of which
currently make up the mirror.


I see myself bying an i3 before too long. Talk about first-world problems.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

When you are fine, don’t worry. It will pass.

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

  parent reply	other threads:[~2017-12-11 23:21 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
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 [this message]
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=20171211232048.GA18223@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