linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Hendrik Friedel" <hendrik@friedels.name>
To: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: raid 5/6 - is this implemented?
Date: Fri, 06 Nov 2020 19:41:11 +0000	[thread overview]
Message-ID: <emd2373acd-6dfe-4317-bdf7-402cb909bc3f@desktop-g0r648m> (raw)

Hello,

I stumbled upon this:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg91938.html

<<This is why scrub after a crash or powerloss with raid56 is important,
while the array is still whole (not degraded). The two problems with
that are:

a) the scrub isn't initiated automatically, nor is it obvious to the
user it's necessary
b) the scrub can take a long time, Btrfs has no partial scrubbing.

Wheras mdadm arrays offer a write intent bitmap to know what blocks to
partially scrub, and to trigger it automatically following a crash or
powerloss.

It seems Btrfs already has enough on-disk metadata to infer a
functional equivalent to the write intent bitmap, via transid. Just
scrub the last ~50 generations the next time it's mounted. Either do
this every time a Btrfs raid56 is mounted. Or create some flag that
allows Btrfs to know if the filesystem was not cleanly shutdown. >>

Has this been implemented in the meantime? If not: Are there any plans 
to?

Regards,
Hendrik


             reply	other threads:[~2020-11-06 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 19:41 Hendrik Friedel [this message]
2020-11-07  1:43 ` raid 5/6 - is this implemented? Zygo Blaxell
2020-11-11 17:06   ` Re[2]: " Hendrik Friedel

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=emd2373acd-6dfe-4317-bdf7-402cb909bc3f@desktop-g0r648m \
    --to=hendrik@friedels.name \
    --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;
as well as URLs for NNTP newsgroup(s).