From: Mark Harmstone <mark@harmstone.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs RAID5 or btrfs on md RAID5?
Date: Tue, 21 Oct 2025 17:45:33 +0100 [thread overview]
Message-ID: <76ac6739-806e-4e6b-acb3-ebfba74cb8f3@harmstone.com> (raw)
In-Reply-To: <a8a16938b9112d7aa68b6df3de30d35c116fb17a.camel@scientia.org>
On 21/10/2025 4.53 pm, Christoph Anton Mitterer wrote:
> On Tue, 2025-10-21 at 16:46 +0100, Mark Harmstone wrote:
>> The brutal truth is probably that RAID5/6 is an idea whose time has
>> passed.
>> Storage is cheap enough that it doesn't warrant the added latency,
>> CPU time,
>> and complexity.
>
> That doesn't seem to be generally the case. We have e.g. large storage
> servers with 24x 22 TB HDDs.
>
> RAID6 is plenty enough redundancy for these, loosing 2 HDDs.
> RAID1 would loose half.
>
>
> Cheers,
> Chris.
So for every sector you want to write, you actually need to write three
and read 21. That seems a very quick way to wear out all those disks.
And then one starts operating more slowly, which slows down every write...
I'd still use RAID1 in this case.
next prev parent reply other threads:[~2025-10-21 16:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:09 btrfs RAID5 or btrfs on md RAID5? Ulli Horlacher
2025-09-22 7:41 ` Qu Wenruo
2025-09-22 8:28 ` Ulli Horlacher
2025-09-22 9:06 ` Qu Wenruo
2025-09-22 9:23 ` Ulli Horlacher
2025-09-22 9:27 ` Qu Wenruo
2025-10-20 9:00 ` Ulli Horlacher
2025-10-20 9:31 ` Andrei Borzenkov
2025-09-22 9:43 ` Ulli Horlacher
2025-09-22 10:41 ` Qu Wenruo
2025-10-21 1:02 ` DanglingPointer
2025-10-21 15:46 ` Mark Harmstone
2025-10-21 15:53 ` Christoph Anton Mitterer
2025-10-21 16:15 ` Jukka Larja
2025-10-21 16:45 ` Mark Harmstone [this message]
2025-10-21 17:32 ` Andrei Borzenkov
2025-10-21 17:43 ` Mark Harmstone
2025-10-21 19:32 ` Goffredo Baroncelli
2025-10-21 22:19 ` DanglingPointer
2025-09-22 8:07 ` Lukas Straub
2025-09-22 8:50 ` Ulli Horlacher
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=76ac6739-806e-4e6b-acb3-ebfba74cb8f3@harmstone.com \
--to=mark@harmstone.com \
--cc=calestyo@scientia.org \
--cc=linux-btrfs@vger.kernel.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 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.