From: Andrea Gelmini <andrea.gelmini@gmail.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Roman Mamedov <rm@romanrm.net>,
Andrei Borzenkov <arvidjaar@gmail.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
Josef Bacik <josef@toxicpanda.com>,
Chris Murphy <lists@colorremedies.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Suggestions for building new 44TB Raid5 array
Date: Mon, 20 Jun 2022 22:37:25 +0200 [thread overview]
Message-ID: <CAK-xaQa0n8q9Fc5-t-pJfu4yrwO28A7dzEOgytzedbhL3N3v-A@mail.gmail.com> (raw)
In-Reply-To: <20220611145259.GF1664812@merlins.org>
Il giorno sab 11 giu 2022 alle ore 16:53 Marc MERLIN
<marc@merlins.org> ha scritto:
> Mmmh, bcachefs, I was not aware of this new one. Not sure if I want to
> add yet another layer, esepcially if it's new.
I share the link just to say: bcache author works in a great way.
Bcachefs could be the idea to replace a few layers. Not to add new
one.
Just for the record.
I'm using a 120TB array with BTRFS and bcache as caching over raid1 2TB ssd.
I tried same setup with LVM, but - sadly - lvm tool complained about
maximum cache size (16GB max, if I remember exactly, anyway no way to
use the fully 2TB).
Sad, because nowhere they mentioned this.
Played a little bit with kernel source, but eventually didn't want to
risk too much with a server I want to use in production at work.
On my side, in the end, I really like cryptsetup for each HD, with
mergerfs and snapraid (for my home setup).
Very handy with replacing, playing, experimenting and so on.
Each time I tried one big single volume setup, eventually I regret it.
Ciao,
Gelma
next prev parent reply other threads:[~2022-06-20 20:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 4:51 Suggestions for building new 44TB Raid5 array Marc MERLIN
2022-06-11 9:30 ` Roman Mamedov
[not found] ` <CAK-xaQYc1PufsvksqP77HMe4ZVTkWuRDn2C3P-iMTQzrbQPLGQ@mail.gmail.com>
2022-06-11 14:52 ` Marc MERLIN
2022-06-11 17:54 ` Roman Mamedov
2022-06-12 17:31 ` Marc MERLIN
2022-06-12 21:21 ` Roman Mamedov
2022-06-13 17:46 ` Marc MERLIN
2022-06-13 18:06 ` Roman Mamedov
2022-06-14 4:51 ` Marc MERLIN
2022-06-13 18:10 ` Zygo Blaxell
2022-06-13 18:13 ` Marc MERLIN
2022-06-13 18:29 ` Roman Mamedov
2022-06-13 20:08 ` Zygo Blaxell
2022-06-14 6:36 ` Torbjörn Jansson
2022-06-20 20:37 ` Andrea Gelmini [this message]
2022-06-21 5:26 ` Zygo Blaxell
2022-07-06 9:09 ` Andrea Gelmini
2022-06-11 23:44 ` Zygo Blaxell
2022-06-14 11:03 ` ronnie sahlberg
[not found] ` <5e1733e6-471e-e7cb-9588-3280e659bfc2@aqueos.com>
2022-06-20 15:01 ` Marc MERLIN
2022-06-20 15:52 ` Ghislain Adnet
2022-06-20 16:27 ` Marc MERLIN
2022-06-20 17:02 ` Andrei Borzenkov
2022-06-20 17:26 ` Marc MERLIN
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=CAK-xaQa0n8q9Fc5-t-pJfu4yrwO28A7dzEOgytzedbhL3N3v-A@mail.gmail.com \
--to=andrea.gelmini@gmail.com \
--cc=arvidjaar@gmail.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=marc@merlins.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=rm@romanrm.net \
/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.