From: Lionel Bouton <lionel-subscription@bouton.name>
To: Florian Lindner <mailinglists@xgm.de>, linux-btrfs@vger.kernel.org
Subject: Re: Convert from RAID 5 to 10
Date: Tue, 29 Nov 2016 20:03:08 +0100 [thread overview]
Message-ID: <d2551840-173a-712b-4039-99854e62539a@bouton.name> (raw)
In-Reply-To: <10bbbf97-7f43-c972-a832-4a8cf054d5e5@xgm.de>
Hi,
Le 29/11/2016 à 18:20, Florian Lindner a écrit :
> [...]
>
> * Any other advice? ;-)
Don't rely on RAID too much... The degraded mode is unstable even for
RAID10: you can corrupt data simply by writing to a degraded RAID10. I
could reliably reproduce this on a 6 devices RAID10 BTRFS filesystem
with a missing device. It affected even a 4.8.4 kernel where our
PostgreSQL clusters got frequent write errors (on the fs itself but not
the 5 working devices) and managed to corrupt their data. Have backups,
you probably will need them.
With Btrfs RAID If you have a failing device, replace it early (monitor
the devices and don't wait for them to fail if you get transient errors
or see worrying SMART values). If you have a failed device, don't
actively use the filesystem in degraded mode. Replace or delete/add
before writing to the filesystem again.
Best regards,
Lionel
next prev parent reply other threads:[~2016-11-29 19:03 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
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 [this message]
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=d2551840-173a-712b-4039-99854e62539a@bouton.name \
--to=lionel-subscription@bouton.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=mailinglists@xgm.de \
/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).