From: Reindl Harald <h.reindl@thelounge.net>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Jeff Allison <jeff.allison@allygray.2y.net>,
linux-raid@vger.kernel.org
Subject: Re: proactive disk replacement
Date: Mon, 20 Mar 2017 16:04:56 +0100 [thread overview]
Message-ID: <c20d279a-62b1-2c3d-cdaf-39a838034afb@thelounge.net> (raw)
In-Reply-To: <11c21a22-4bbf-7b16-5e64-8932be768c68@websitemanagers.com.au>
Am 20.03.2017 um 15:59 schrieb Adam Goryachev:
> On 20/3/17 23:47, Jeff Allison wrote:
>> Hi all I’ve had a poke around but am yet to find something definitive.
>>
>> I have a raid 5 array of 4 disks amounting to approx 5.5tb. Now this
>> disks are getting a bit long in the tooth so before I get into
>> problems I’ve bought 4 new disks to replace them.
>>
>> I have a backup so if it all goes west I’m covered. So I’m looking for
>> suggestions.
>>
>> My current plan is just to replace the 2tb drives with the new 3tb
>> drives and move on, I’d like to do it on line with out having to trash
>> the array and start again, so does anyone have a game plan for doing
>> that.
> Yes, do not fail a disk and then replace it, use the newer replace
> method (it keeps redundancy in the array)
how should it keep redundancy when you have to remove a disk anyways
except you have enough slots to at least temporary add a additional one?
next prev parent reply other threads:[~2017-03-20 15:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 12:47 proactive disk replacement Jeff Allison
2017-03-20 13:25 ` Reindl Harald
2017-03-20 14:59 ` Adam Goryachev
2017-03-20 15:04 ` Reindl Harald [this message]
2017-03-20 15:23 ` Adam Goryachev
2017-03-20 16:19 ` Wols Lists
2017-03-21 2:33 ` Jeff Allison
2017-03-21 9:54 ` Reindl Harald
2017-03-21 10:54 ` Adam Goryachev
2017-03-21 11:03 ` Reindl Harald
2017-03-21 11:34 ` Andreas Klauer
2017-03-21 12:03 ` Reindl Harald
2017-03-21 12:41 ` Andreas Klauer
2017-03-22 4:16 ` NeilBrown
2017-03-21 11:56 ` Adam Goryachev
2017-03-21 12:10 ` Reindl Harald
2017-03-21 13:13 ` David Brown
2017-03-21 13:24 ` Reindl Harald
2017-03-21 14:15 ` David Brown
2017-03-21 15:25 ` Wols Lists
2017-03-21 15:41 ` David Brown
2017-03-21 16:49 ` Phil Turmel
2017-03-22 13:53 ` Gandalf Corvotempesta
2017-03-22 14:12 ` David Brown
2017-03-22 14:32 ` Phil Turmel
2017-03-21 11:55 ` Gandalf Corvotempesta
2017-03-21 13:02 ` David Brown
2017-03-21 13:26 ` Gandalf Corvotempesta
2017-03-21 14:26 ` David Brown
2017-03-21 15:31 ` Wols Lists
2017-03-21 17:00 ` Phil Turmel
2017-03-21 15:29 ` Wols Lists
2017-03-21 16:55 ` Phil Turmel
2017-03-22 14:51 ` John Stoffel
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=c20d279a-62b1-2c3d-cdaf-39a838034afb@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=jeff.allison@allygray.2y.net \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
/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.