All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Wilson Meier <wilson.meier@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
	"Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Convert from RAID 5 to 10
Date: Wed, 30 Nov 2016 10:38:08 +0500	[thread overview]
Message-ID: <20161130103808.74e5ae95@natsu> (raw)
In-Reply-To: <fce2df8b-0775-1ecf-c08d-960018822c20@googlemail.com>

On Wed, 30 Nov 2016 00:16:48 +0100
Wilson Meier <wilson.meier@gmail.com> wrote:

> That said, btrfs shouldn't be used for other then raid1 as every other
> raid level has serious problems or at least doesn't work as the expected
> raid level (in terms of failure recovery).

RAID1 shouldn't be used either:

*) Read performance is not optimized: all metadata is always read from the
first device unless it has failed, data reads are supposedly balanced between
devices per PID of the process reading. Better implementations dispatch reads
per request to devices that are currently idle.

*) Write performance is not optimized, during long full bandwidth sequential
writes it is common to see devices writing not in parallel, but with a long
periods of just one device writing, then another. (Admittedly have been some
time since I tested that).

*) A degraded RAID1 won't mount by default.

If this was the root filesystem, the machine won't boot.

To mount it, you need to add the "degraded" mount option.
However you have exactly a single chance at that, you MUST restore the RAID to
non-degraded state while it's mounted during that session, since it won't ever
mount again in the r/w+degraded mode, and in r/o mode you can't perform any
operations on the filesystem, including adding/removing devices.

*) It does not properly handle a device disappearing during operation. (There
is a patchset to add that).

*) It does not properly handle said device returning (under a
different /dev/sdX name, for bonus points).

Most of these also apply to all other RAID levels.

-- 
With respect,
Roman

  parent reply	other threads:[~2016-11-30  5:38 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 [this message]
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
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=20161130103808.74e5ae95@natsu \
    --to=rm@romanrm.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.