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: [gentoo-user] [OT] Using an odd number of drives in ZFS RaidZ
Date: Tue, 29 Jun 2021 15:56:49 +0200	[thread overview]
Message-ID: <YNsmobeqhBMEJWcM@moby> (raw)

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

Hello fellows

This is not really a Gentoo question, but at least my NAS (which this mail
is about) is running Gentoo. :)

There are some people amongst this esteemed group that know their stuff
about storage and servers and things, so I thought I might try my luck here.
I’ve already looked on the Webs, but my question is a wee bit specific and I
wasn’t able to find the exact answer (yet). And I’m a bit hesitant to ask
this newbie-ish question in a ZFS expert forum. ;-)

Prologue:
Due to how records are distributed across blocks in a parity-based ZFS vdev,
it is recommended to use 2^n data disks. Technically, it is perfectly fine
to deviate from it, but for performance reasons (mostly space efficiency) it
is not the recommended way. That’s because the (default) maximum record size
of 128 k itself is a power of 2 and thus can be distributed evenly on all
drives. At least that’s my understanding. Is that correct?

So here’s the question:
If I had three data drives, (c|w)ould I get around that problem by setting a
record size that is divisible by 3, like 96 k, or even 3 M?



Here’s the background of my question:
Said NAS is based on a Mini-ITX case which has only four drive slots (which
is the most common configuration for a case of this formfactor). I started
with two 6 TB drives, running in a mirror configuration. One year later
space was running out and I filled the remaining slots. To maximise
reliability, I went with RaidZ2.

I reached 80 % usage (which is the recommended maximum for ZFS) and am
now evaluating my options for the coming years.
1) Reduce use of space by re-encoding. My payload is mainly movies, among
   which are 3 TB of DVDs which can be shrunk by at least ⅔ by re-encoding.
   → this takes time and computing effort, but is a long-term goal anyway.
2) Replace all drives with bigger ones. There are three counter arguments:
   • 1000 € for four 10 TB drives (the biggest size available w/o helium)
   • they are only available with 7200 rpm (more power, noise and heat)
   • I am left with four perfectly fine 6 TB drives
3) Go for 4+2 RaidZ2. This requires a bigger case (with new PSU due to
   different form factor) and a SATA expansion card b/c the Mobo only has
   six connectors (I need at least one more for the system drive), costing
   250 € plus drives.
4) Convert to RaidZ1. Gain space of one drive at the cost of resilience. I
   can live with the latter; the server only runs occasionally and not for
   very long at a time. *** This option brings me to my question above,
   because it is easy to achieve and costs no €€€.

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

In this sentance are definately three error’s!

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

             reply	other threads:[~2021-06-29 13:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 13:56 Frank Steinmetzger [this message]
2021-06-30 20:00 ` [gentoo-user] [OT] Using an odd number of drives in ZFS RaidZ antlists
2021-06-30 23:31   ` Frank Steinmetzger
2021-06-30 20:45 ` Neil Bothwick
2021-06-30 23:31   ` Frank Steinmetzger
2021-07-01  1:29     ` William Kenworthy
2021-07-02 15:09       ` J. Roeleveld
2021-07-01 15:07     ` antlists
2021-07-01 17:21       ` Frank Steinmetzger
2021-07-01 13:47 ` Robert David
2021-07-01 15:01   ` antlists
2021-07-01 17:35     ` Frank Steinmetzger
2021-07-04 10:56     ` Robert David
2021-07-02 15:13   ` J. Roeleveld

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=YNsmobeqhBMEJWcM@moby \
    --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