From: Red Wil <redwil@gmail.com>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Replacing all disks in a an array as a preventative measure before failing.
Date: Wed, 9 Feb 2022 16:15:42 -0500 [thread overview]
Message-ID: <20220209161542.544496ce@falcon.sitarc.ca> (raw)
In-Reply-To: <bb5b9cb3-8f74-3194-1193-2108a39d6cdb@turmel.org>
On Wed, 9 Feb 2022 09:57:25 -0500
Phil Turmel <philip@turmel.org> wrote:
> On 2/7/22 15:26, Red Wil wrote:
> > Hello,
>
> [trim/]
>
> > Approaches/solutions and critique
> > 1- add one by one a 'spare' and 'replace' raid member
> > critique:
> > - seem to me long and tedious process
> > - cannot/will not run in parallel
> > 2- add all the spares at once and perform 'replace' on members
> > critique
> > - just tedious - lots of cli commands which can be prone to
> > mistakes. next ones assume I have all the 'spares' in the rig
> > 3- create new arrays on spares, fresh fs and copy data.
> > 4- dd/ddrescue copy each drive to a new one. Advantage can be
> > done one by one or in parallel. less commands in the terminal.
>
> My last drive upgrades were done in a chassis that had two extra hot
> swap bays. So I could do two at a time. I wanted to keep careful
> track of roles, so I started a replace after each spare added, to
> ensure that spare would get the designated role. After it was
> running, I would --add and --replace the next. After the first two
> were running (staggered), it was just waiting for one to finish to
> pop it out and start the next.
>
> After completion, I used --grow to occupy the new space on each.
>
> Took several days, but no downtime at all.
>
> Phil
Hello Phil,
My current chassis is full (no space at all) but I found another
chassis I could use to temporary extend my chassis for the duration of
the swap by using two SAS HBAs and use all 22 drives at once.
Thanks
Red
prev parent reply other threads:[~2022-02-09 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 20:26 Replacing all disks in a an array as a preventative measure before failing Red Wil
2022-02-07 22:28 ` Wol
2022-02-09 20:58 ` Red Wil
2022-02-09 13:02 ` Roger Heflin
2022-02-09 21:07 ` Red Wil
2022-02-09 14:57 ` Phil Turmel
2022-02-09 21:15 ` Red Wil [this message]
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=20220209161542.544496ce@falcon.sitarc.ca \
--to=redwil@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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;
as well as URLs for NNTP newsgroup(s).