From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Marat Khalili <mkh@rqc.ru>,
Patrik Lundquist <patrik.lundquist@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Please help with exact actions for raid1 hot-swap
Date: Mon, 11 Sep 2017 08:49:16 -0400 [thread overview]
Message-ID: <dba3c5d5-b196-ddac-dcd2-01dee95a6f38@gmail.com> (raw)
In-Reply-To: <BB503B0C-5A1A-4ADE-9EDA-B07D9C6DA138@rqc.ru>
On 2017-09-10 02:33, Marat Khalili wrote:
> It doesn't need replaced disk to be readable, right? Then what prevents same procedure to work without a spare bay?
>
In theory, nothing.
In practice, there are reliability issues with mounting a filesystem
degraded (and you should be avoiding running any array degraded,
regardless of if it's BTRFS or actual RAID (be that LVM, MD, or
hardware)). It's also significantly faster to do it with a spare drive
bay because that will just read from the device being replaced and copy
data directly, while pulling the device to be replaced requires
rebuilding the data (there is more involved than just copying, even with
a raid1 profile).
next prev parent reply other threads:[~2017-09-11 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 7:46 Please help with exact actions for raid1 hot-swap Marat Khalili
2017-09-09 9:05 ` Patrik Lundquist
2017-09-09 10:05 ` Marat Khalili
2017-09-09 10:29 ` Patrik Lundquist
2017-09-09 12:19 ` Duncan
2017-09-10 6:33 ` Marat Khalili
2017-09-10 9:17 ` Patrik Lundquist
2017-09-11 12:49 ` Austin S. Hemmelgarn [this message]
2017-09-11 13:16 ` Marat Khalili
2017-09-11 15:11 ` Austin S. Hemmelgarn
2017-09-11 21:33 ` Duncan
2017-09-12 12:33 ` Austin S. Hemmelgarn
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=dba3c5d5-b196-ddac-dcd2-01dee95a6f38@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mkh@rqc.ru \
--cc=patrik.lundquist@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 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).