public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: What's the status of BTRFS RST instead of linux md raid5?
Date: Mon, 13 Apr 2026 09:55:41 -0700	[thread overview]
Message-ID: <ad0gDVe4bwS-zBle@merlins.org> (raw)
In-Reply-To: <955a6526-96a9-4282-895e-d881d0411dea@wdc.com>

On Mon, Apr 13, 2026 at 01:37:30PM +0200, Johannes Thumshirn wrote:
> 
> RST is still considered experimental and the development on the RAID5/6
> support is unfortunately delayed due to different more urgent fires that
> have to be extinguished.
> 
> Note while RST can handle non zoned devices, it's primary focus always was
> always to enable RAID on zoned block devices. Which it does for RAID0, RAID1
> and RAID10.
> 
> As for RAID5 I have a prototype doing writes and reads for the trivial cases
> (i.e. full stripe write/read).
> 
> 
> My apologies to everyone waiting for this. I haven't abandoned the project,
> I just need more time to get it done.
> 
> If you're looking for documentation please have a look here: https://github.com/kdave/btrfs-progs/blob/devel/Documentation/dev/design-raid-stripe-tree.txt

Thank you so much for the status update, *much* appreciated.
As for when, this is all unpaid work I assume, so it gets done when it
gets done, no worries.

For what it's worth, I've ben doing mdadm raid5 with btrfs since 2014,
and unfortuantely it's failed in too many ways, almost each time causing
a btrfs filesystem that was impossible to recover (usually ro mount was
ok, but impossible to get back in read/write state, which is very
inconvenient for a 20TB+ filesystem dueto how long it takes to restore
backups)

As luck would have it, this just happened to me again
https://yhbt.net/lore/linux-btrfs/advYoKqUCUmD4oO6@merlins.org/

I know I don't know the deep insides of the btrfs code, but it's
unfortunately failed enough times on top of mdadm raid5 that I can't
wait to switch to RST when it's ready.  It's been 12 years already, so I
can wait a bit longer still :)

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

      reply	other threads:[~2026-04-13 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 23:10 What's the status of BTRFS RST instead of linux md raid5? Marc MERLIN
2026-04-13 11:37 ` Johannes Thumshirn
2026-04-13 16:55   ` Marc MERLIN [this message]

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=ad0gDVe4bwS-zBle@merlins.org \
    --to=marc@merlins.org \
    --cc=johannes.thumshirn@wdc.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox