linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: and again: broken RAID5
Date: Fri, 11 May 2012 11:28:57 +0100	[thread overview]
Message-ID: <4FACE9E9.2060902@anonymous.org.uk> (raw)
In-Reply-To: <20120510204516.16571810@notabene.brown>

On 10/05/2012 11:45, NeilBrown wrote:
> On Thu, 10 May 2012 11:19:30 +0100 John Robinson
> <john.robinson@anonymous.org.uk>  wrote:
>
>> On 10/05/2012 10:20, NeilBrown wrote:
[...]
>>> Just add --force the to --assemble command.
>>
>> I think I'd assemble from only 3 drives, sdh, sdf and sdj, because sdi's
>> event count is so much lower it must be the one that was knocked out
>> first and you probably want to resync onto it (or a fresh drive if it's
>> actually faulty).
>
> correct.  And that is exactly what "mdadm --assemble --force" will decide
> too. :-)
> It will assemble from h, f, j and exclude i.

Ah - I didn't know it was clever enough to do that, I had assumed that 
if you forced all the drives they'd all be marked up-to-date.

What should I do if I had 3 different event counts (like this case) all 
fairly close to each other (unlike this case) and I really did want to 
force them all, avoiding a resync?

Cheers,

John.

  reply	other threads:[~2012-05-11 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10  8:07 and again: broken RAID5 Lars Schimmer
2012-05-10  9:20 ` NeilBrown
2012-05-10 10:19   ` John Robinson
2012-05-10 10:45     ` NeilBrown
2012-05-11 10:28       ` John Robinson [this message]
2012-05-11  7:27   ` Lars Schimmer

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=4FACE9E9.2060902@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).