From: NeilBrown <neilb@suse.de>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
fdmanana@gmail.com, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: RAID5/6 permanent corruption of metadata and data extents
Date: Sun, 05 Apr 2020 07:15:38 +1000 [thread overview]
Message-ID: <87zhbrvtol.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20200404145846.GK13306@hungrycats.org>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Sat, Apr 04 2020, Zygo Blaxell wrote:
> mdadm does one thing very well, but only the one thing. I don't imagine
> Neil would extend mdadm to the point where it can handle handle silent
You are correct, I wouldn't.
md provides a block devices, btrfs provides a filesystem. They are
totally different things. Saying that btrfs/RAID6 is "better" than
mdadm/raid6 is like saying the ext4 is "better" than a SCSI drive. It
doesn't really mean anything.
I could argue that calling what btrfs does "RAID6" is misleading and
possibly the cause of confusion. I think the decision to call what ZFS
does "RAID-Z" was probably a good idea - it is somewhat like RAID, but
on a whole new level. Maybe the stuff btrfs does could be RAID-B :-)
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-04 21:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 11:08 RAID5/6 permanent corruption of metadata and data extents Filipe Manana
2020-04-02 11:55 ` Qu Wenruo
2020-04-02 12:33 ` Filipe Manana
2020-04-02 12:43 ` Qu Wenruo
2020-04-02 13:26 ` Filipe Manana
2020-04-03 0:00 ` Qu Wenruo
2020-04-03 4:02 ` Zygo Blaxell
2020-04-03 10:04 ` Filipe Manana
2020-04-03 10:11 ` Qu Wenruo
2020-04-03 10:49 ` Filipe Manana
2020-04-03 12:16 ` Qu Wenruo
2020-04-03 16:32 ` Goffredo Baroncelli
2020-04-03 16:40 ` Filipe Manana
2020-04-02 21:14 ` Zygo Blaxell
2020-04-03 7:20 ` Andrea Gelmini
2020-04-04 14:58 ` Zygo Blaxell
2020-04-04 15:45 ` Martin Raiber
2020-04-04 21:15 ` NeilBrown [this message]
2020-04-02 19:56 ` Goffredo Baroncelli
2020-04-02 22:14 ` Zygo Blaxell
2020-04-02 21:02 ` Zygo Blaxell
2020-04-03 9:58 ` Filipe Manana
2020-04-04 13:09 ` Zygo Blaxell
2020-04-04 18:17 ` Zygo Blaxell
2020-04-02 23:52 ` Chris Murphy
2020-04-06 12:13 ` Anand Jain
2020-04-06 16:25 ` Filipe Manana
2020-04-07 2:10 ` Zygo Blaxell
2020-04-07 10:58 ` Filipe Manana
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=87zhbrvtol.fsf@notabene.neil.brown.name \
--to=neilb@suse.de \
--cc=andrea.gelmini@gmail.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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.