From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-raid@vger.kernel.org
Subject: add vs. re-add
Date: Sun, 10 Aug 2014 23:50:11 +0200 [thread overview]
Message-ID: <20140810215011.GA16750@lazy.lzy> (raw)
Hi all,
maybe this was already explained, but I could not
find something specific.
Given a parity array (RAID-456) with bitmap, when
add HDD accidentally disconnects, it can be re-added.
That is, only the bitmapped changes are synchronized.
Now, sometimes this is not possible, that is the
disk *must* be added, with full synchronization.
Questions:
1) What's the criteria used by "mdadm" to decide if
an HDD can be re-added or it must be added?
2) Knowing that the HDD can be re-added, can be this
forced? (I did *not* try --force).
Thanks,
bye,
--
piergiorgio
reply other threads:[~2014-08-10 21:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140810215011.GA16750@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--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).