From: Roger Heflin <rogerheflin@gmail.com>
To: David T-G <davidtg-robot@justpickone.org>
Cc: Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: re-add syntax
Date: Thu, 21 May 2020 13:40:56 -0500 [thread overview]
Message-ID: <CAAMCDecB+CU-EGtx+4bMPKBYcy65sgT-8MW=s=OeviyZeq6URA@mail.gmail.com> (raw)
In-Reply-To: <20200521180700.GT1415@justpickone.org>
For re-add to work the array must have a bitmap, so that mdadm knows
what parts of the disk need updating.
mine looks like this:
md13 : active raid6 sdi3[9] sdf3[12] sdg3[6] sdd3[1] sdc3[5] sdb3[7] sde3[10]
3612623360 blocks super 1.2 level 6, 512k chunk, algorithm 2
[7/7] [UUUUUUU]
bitmap: 0/6 pages [0KB], 65536KB chunk
On Thu, May 21, 2020 at 1:10 PM David T-G <davidtg-robot@justpickone.org> wrote:
>
> Hi, all --
>
> ...and then davidtg-robot@justpickone.org said...
> %
> % ...and then antlists said...
> % %
> % % So *you* should choose re-add. Let mdadm choose add if it can't do a re-add.
> %
> % Thanks. Sooooo ... Given this
> ...
> % does this
> %
> % mdadm --manage /dev/md0 --re-add /dev/sdd1
> %
> % look like the right next step?
>
> Perhaps it did, but it wasn't to be:
>
> diskfarm:root:10:~> mdadm --manage /dev/md0 --re-add /dev/sdd1
> mdadm: --re-add for /dev/sdd1 to /dev/md0 is not possible
>
> So we'll try "add"
>
> diskfarm:root:10:~> mdadm --manage /dev/md0 --add /dev/sdd1
> mdadm: added /dev/sdd1
>
> and now we wait :-)
>
>
> Thanks again to all
>
> :-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 18:40 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 ` re-add syntax David T-G
2020-05-21 18:07 ` David T-G
2020-05-21 18:40 ` Roger Heflin [this message]
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='CAAMCDecB+CU-EGtx+4bMPKBYcy65sgT-8MW=s=OeviyZeq6URA@mail.gmail.com' \
--to=rogerheflin@gmail.com \
--cc=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 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.