Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: RAID-[56] stabilisation
Date: Wed, 20 Apr 2022 10:17:09 +0800	[thread overview]
Message-ID: <a59b507b-f528-472b-29c9-da2e62deaad9@gmx.com> (raw)
In-Reply-To: <22677769.8507095.1650409322744.JavaMail.zimbra@karlsbakk.net>



On 2022/4/20 07:02, Roy Sigurd Karlsbakk wrote:
> Hi all
>
> It's been a wee bit more than a decade since I started to look into btrfs as a possible ZFS replacement. I just wonder when one can expect RAID-[56] to stabilise as in usable for production, since this is, for my use, rather critial.

Currently the main problem for btrfs RAID56 is write-hole.

To solve it, either we need a big feature in extent allocator (to avoid
allocate extents in the partial written stripe), or go traditional
journal based RAID56 (needs a new on-disk format change, and new code).


If your use case can rule out power loss (by using UPS) and unexpected
shutdown (no way to prevent kernel panic though), OR you can afford a
full btrfs scrub before any write (can be very time consuming), you can
try btrfs RAID56.

There is some plan to implement a RAID56 journal, but there is no
concrete time table for that yet.


Or, you can run single device btrfs on md/dm-raid56.

Thanks,
Qu

>
> Vennlig hilsen / Best regards
>
> roy
> --
> Roy Sigurd Karlsbakk
> (+47) 98013356
> http://blogg.karlsbakk.net/
> GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
> --
> I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.

  reply	other threads:[~2022-04-20  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 23:02 RAID-[56] stabilisation Roy Sigurd Karlsbakk
2022-04-20  2:17 ` Qu Wenruo [this message]
2022-04-20  2:19   ` Qu Wenruo

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=a59b507b-f528-472b-29c9-da2e62deaad9@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=roy@karlsbakk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox