From: Wols Lists <antlists@youngman.org.uk>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: 3-way mirror to RAID-6
Date: Mon, 8 Jan 2018 15:20:14 +0000 [thread overview]
Message-ID: <5A538C2E.70400@youngman.org.uk> (raw)
In-Reply-To: <CAJH6TXj-6hyq2BM4GF0YdYQ27DAembZY0cLUt+BZKo+YySfGOw@mail.gmail.com>
On 08/01/18 11:34, Gandalf Corvotempesta wrote:
> So, which is the best procedure to follow to increse the total usable
> space, without loosing redundancy while the system is running ?
>
> I would like to have some confirms from skilled users in this ML.
> On my own, i would replace one disk per time (fail+remove+add) and
> wait for resync to complete, then, resize the array:
Well, that's certainly not best practice!
If you can, you replace one disk at a time with --replace. That will
copy the drive in-place with *no* reduction in redundancy. Doing a
fail/remove removes one level of redundancy.
Okay, you need spare ports to do a --replace so it's not always
possible, but it's always desirable. And with enough spare ports, you
can replace more than one drive at once, again with NO loss of redundancy.
Cheers,
Wol
next prev parent reply other threads:[~2018-01-08 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 19:36 3-way mirror to RAID-6 Gandalf Corvotempesta
2017-12-25 21:53 ` NeilBrown
2017-12-26 10:09 ` Wols Lists
2017-12-27 10:13 ` Gandalf Corvotempesta
2017-12-27 14:28 ` Phil Turmel
[not found] ` <CAJH6TXiqsd=Zs4t5qAEe19shJFgSAZ1W-95yT041H6OyLbKvfA@mail.gmail.com>
2017-12-28 12:34 ` Phil Turmel
2018-01-08 11:34 ` Gandalf Corvotempesta
2018-01-08 15:20 ` Wols Lists [this message]
2018-01-08 15:25 ` Gandalf Corvotempesta
2018-01-08 20:18 ` Wol's lists
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=5A538C2E.70400@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gandalf.corvotempesta@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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