From: Martin Steigerwald <martin@lichtvoll.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Wilson Meier <wilson.meier@gmail.com>,
Duncan <1i5t5.duncan@cox.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Convert from RAID 5 to 10
Date: Wed, 30 Nov 2016 20:36:51 +0100 [thread overview]
Message-ID: <2106513.UkuxMIuvWQ@merkaba> (raw)
In-Reply-To: <CAJCQCtRnqp15QZ9V+AtBu1_7QwChdoRMs0nHg3stWnJOyy8qMw@mail.gmail.com>
Am Mittwoch, 30. November 2016, 12:09:23 CET schrieb Chris Murphy:
> On Wed, Nov 30, 2016 at 7:37 AM, Austin S. Hemmelgarn
>
> <ahferroin7@gmail.com> wrote:
> > The stability info could be improved, but _absolutely none_ of the things
> > mentioned as issues with raid1 are specific to raid1. And in general, in
> > the context of a feature stability matrix, 'OK' generally means that there
> > are no significant issues with that specific feature, and since none of
> > the
> > issues outlined are specific to raid1, it does meet that description of
> > 'OK'.
>
> Maybe the gotchas page needs a one or two liner for each profile's
> gotchas compared to what the profile leads the user into believing.
> The overriding gotcha with all Btrfs multiple device support is the
> lack of monitoring and notification other than kernel messages; and
> the raid10 actually being more like raid0+1 I think it certainly a
> gotcha, however 'man mkfs.btrfs' contains a grid that very clearly
> states raid10 can only safely lose 1 device.
Wow, that manpage is quite an resource.
Developers, documentation people definitely improved the official BTRFS
documentation.
Thanks,
--
Martin
next prev parent reply other threads:[~2016-11-30 19:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 17:20 Convert from RAID 5 to 10 Florian Lindner
2016-11-29 17:54 ` Austin S. Hemmelgarn
2016-11-29 22:34 ` Wilson Meier
2016-11-29 22:52 ` Chris Murphy
2016-11-29 23:16 ` Wilson Meier
2016-11-29 23:49 ` Chris Murphy
2016-11-29 23:58 ` Wilson Meier
2016-11-30 5:38 ` Roman Mamedov
2016-11-30 8:06 ` Martin Steigerwald
2016-11-30 8:35 ` Wilson Meier
2016-11-30 10:41 ` Duncan
2016-11-30 13:12 ` Wilson Meier
2016-11-30 14:37 ` Austin S. Hemmelgarn
2016-11-30 15:49 ` Wilson Meier
2016-11-30 16:35 ` Martin Steigerwald
2016-11-30 16:48 ` Austin S. Hemmelgarn
2016-12-01 6:47 ` Duncan
2016-12-01 9:37 ` Wilson Meier
2016-12-01 11:36 ` Niccolò Belli
2016-11-30 19:09 ` Chris Murphy
2016-11-30 19:36 ` Martin Steigerwald [this message]
2016-11-30 20:29 ` Tomasz Kusmierz
2016-12-01 17:28 ` Chris Murphy
2016-12-01 21:40 ` Tomasz Kusmierz
2016-11-30 16:09 ` Niccolò Belli
2016-11-30 12:50 ` Austin S. Hemmelgarn
2016-11-30 14:04 ` Roman Mamedov
2016-11-30 15:43 ` Austin S. Hemmelgarn
2016-11-30 18:59 ` Chris Murphy
2016-11-29 19:03 ` Lionel Bouton
2016-11-29 19:41 ` Austin S. Hemmelgarn
2016-12-06 14:14 ` Florian Lindner
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=2106513.UkuxMIuvWQ@merkaba \
--to=martin@lichtvoll.de \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=wilson.meier@gmail.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.