From: Marc MERLIN <marc@merlins.org>
To: Andrea Gelmini <andrea.gelmini@gmail.com>,
Roman Mamedov <rm@romanrm.net>
Cc: 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: Sat, 11 Jun 2022 07:52:59 -0700 [thread overview]
Message-ID: <20220611145259.GF1664812@merlins.org> (raw)
In-Reply-To: <20220611143033.56ffa6af@nvm> <20220611143033.56ffa6af@nvm> <CAK-xaQYc1PufsvksqP77HMe4ZVTkWuRDn2C3P-iMTQzrbQPLGQ@mail.gmail.com>
On Sat, Jun 11, 2022 at 09:27:57AM +0200, Andrea Gelmini wrote:
> Il giorno sab 11 giu 2022 alle ore 09:16 Marc MERLIN
> <marc@merlins.org> ha scritto:
> > As for bcache, I'm really thinking about droppping it, unless I'm told
> > it should be safe to use.
>
> https://lwn.net/Articles/895266/
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.
On Sat, Jun 11, 2022 at 02:30:33PM +0500, Roman Mamedov wrote:
> > 2) echo 0fb96f02-d8da-45ce-aba7-070a1a8420e3 > /sys/block/bcache64/bcache/attach
> > gargamel:/dev# cat /sys/block/md7/bcache/cache_mode
> > [writethrough] writeback writearound none
>
> Maybe try LVM Cache this time?
Hard to know either way, trading one layer for another, and LVM has
always seemed heavier
> > 3) cryptsetup luksFormat --align-payload=2048 -s 256 -c aes-xts-plain64 /dev/bcache64
> > 4) cryptsetup luksOpen /dev/bcache64 dshelf1
>
> What's the threat scenario for LUKS on the array?
In case my computer gets stolen, and indeed being able to recycle old
drives without having to worry, is a nice bonus.
> > 5) mkfs.btrfs -m dup -L dshelf1 /dev/mapper/dshelf1
>
> Personally I have switched from Btrfs on MD to individual disks and MergerFS.
That gives you no redundancy if a drive disk, correct?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
next prev parent reply other threads:[~2022-06-11 14:53 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 [this message]
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
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=20220611145259.GF1664812@merlins.org \
--to=marc@merlins.org \
--cc=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=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.