From: Neil Brown <neilb@suse.de>
To: "Ceuleers, Jan (Jan)" <jan.ceuleers@alcatel-lucent.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Need help with recovery
Date: Thu, 15 Jul 2010 23:40:58 +1000 [thread overview]
Message-ID: <20100715234058.0f580546@nbeee.brown> (raw)
In-Reply-To: <BCD693DB5C9A3349A6F7694398FA08E21D46103209@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
On Thu, 15 Jul 2010 11:50:56 +0200
"Ceuleers, Jan (Jan)" <jan.ceuleers@alcatel-lucent.com> wrote:
> Neil,
>
> > mdadm -A /dev/md2 --force /dev/sd[ade]2
>
> Many thanks for your feedback. I will try this when I get home.
>
> So if I boil this down to the principles, your advice is to assemble
> the array in degraded mode using the components that have the most
> recent update timestamps. Degraded, because this prevents
> resynchronisation.
>
It is more a case of "degraded because that uses fewer devices, and
so fewer old devices which could introduce errors." though avoiding
resync is a good thing too.
The key bit is "--force" which tell mdadm to assemble it anyway
even if something looks out of data. mdadm will only include just
enough devices to make the array work.
You don't really need to be selective about the devices you
choose. If you give "mdadm -Af" all of the devices, it will just
pick the ones that are best. I just listed them for you to
make it more clear what was happening.
NeilBrown
next prev parent reply other threads:[~2010-07-15 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 14:37 Need help with recovery Jan Ceuleers
2010-07-15 5:37 ` Neil Brown
2010-07-15 9:50 ` Ceuleers, Jan (Jan)
2010-07-15 13:40 ` Neil Brown [this message]
2010-07-15 19:27 ` Jan Ceuleers
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=20100715234058.0f580546@nbeee.brown \
--to=neilb@suse.de \
--cc=jan.ceuleers@alcatel-lucent.com \
--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.