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
