All of lore.kernel.org
 help / color / mirror / Atom feed
From: antlists <antlists@youngman.org.uk>
To: David T-G <davidtg-robot@justpickone.org>,
	Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: re-add syntax (was "Re: failed disks, mapper, and "Invalid argument"")
Date: Thu, 21 May 2020 14:01:08 +0100	[thread overview]
Message-ID: <828a3b59-f79c-a205-3e1e-83e34ae93eac@youngman.org.uk> (raw)
In-Reply-To: <20200521123306.GO1415@justpickone.org>

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.

So *you* should choose re-add. Let mdadm choose add if it can't do a re-add.

Cheers,
Wol

  reply	other threads:[~2020-05-21 13:01 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 [this message]
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
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=828a3b59-f79c-a205-3e1e-83e34ae93eac@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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.