From: David T-G <davidtg-robot@justpickone.org>
To: Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: re-add syntax
Date: Thu, 21 May 2020 09:15:00 -0400 [thread overview]
Message-ID: <20200521131500.GP1415@justpickone.org> (raw)
In-Reply-To: <828a3b59-f79c-a205-3e1e-83e34ae93eac@youngman.org.uk>
Wol, et al (is there anyone else, even??) --
...and then antlists said...
%
% On 21/05/2020 13:33, David T-G wrote:
% >% Can't remember the syntax, but there's a re-add option. If it can find
% >% and replay a log of failed updates, it will bring the drive straight
% >% back in. Otherwise it will rebuild from scratch.
% >%
% >% That's probably the safest way - let mdadm choose the best option.
% >
% >OK; yay. I'm still confused, though, between "add" and "readd". I'll
% >take any pointers to docs I can get.
%
% Add just adds the drive back and rebuilds it.
%
% Readd will play a journal if it can. If it can't, it will fall back
% and do an add.
OK. Sounds good.
%
% So *you* should choose re-add. Let mdadm choose add if it can't do a re-add.
Thanks. Sooooo ... Given this
diskfarm:root:10:~> cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdb1[0] sda1[4] sdc1[3]
11720265216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [U_UU]
md127 : active raid5 sdf2[0] sdg2[1] sdh2[3]
1464622080 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
unused devices: <none>
diskfarm:root:10:~> mdadm --examine /dev/sd[abcd]1 | egrep '/dev/sd|Event'
/dev/sda1:
Events : 57862
/dev/sdb1:
Events : 57862
/dev/sdc1:
Events : 57862
/dev/sdd1:
Events : 48959
does this
mdadm --manage /dev/md0 --re-add /dev/sdd1
look like the right next step?
%
% Cheers,
% Wol
Thanks again & HAND
:-D
--
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
next prev parent reply other threads:[~2020-05-21 13:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 20:05 failed disks, mapper, and "Invalid argument" David T-G
2020-05-20 23:23 ` Wols Lists
2020-05-20 23:53 ` David T-G
2020-05-21 8:09 ` Wols Lists
2020-05-21 11:01 ` David T-G
2020-05-21 11:55 ` Wols Lists
2020-05-21 12:30 ` disks & prices plus python (was "Re: failed disks, mapper, and "Invalid argument"") David T-G
2020-05-21 13:07 ` antlists
2020-05-21 13:17 ` disks & prices plus python David T-G
2020-05-21 13:42 ` Wols Lists
2020-05-21 13:46 ` David T-G
2020-05-21 11:01 ` failed disks, mapper, and "Invalid argument" David T-G
2020-05-21 11:24 ` David T-G
2020-05-21 12:00 ` Wols Lists
2020-05-21 12:33 ` re-add syntax (was "Re: failed disks, mapper, and "Invalid argument"") David T-G
2020-05-21 13:01 ` antlists
2020-05-21 13:15 ` David T-G [this message]
2020-05-21 18:07 ` re-add syntax David T-G
2020-05-21 18:40 ` Roger Heflin
2020-05-21 22:52 ` David T-G
2020-05-21 23:17 ` antlists
2020-05-21 23:53 ` David T-G
2020-05-21 8:13 ` failed disks, mapper, and "Invalid argument" Wols Lists
2020-05-21 11:04 ` David T-G
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=20200521131500.GP1415@justpickone.org \
--to=davidtg-robot@justpickone.org \
--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;
as well as URLs for NNTP newsgroup(s).