From: NeilBrown <neilb@suse.de>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: Lars Schimmer <l.schimmer@cgv.tugraz.at>, linux-raid@vger.kernel.org
Subject: Re: and again: broken RAID5
Date: Thu, 10 May 2012 20:45:16 +1000 [thread overview]
Message-ID: <20120510204516.16571810@notabene.brown> (raw)
In-Reply-To: <4FAB9632.5010206@anonymous.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
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:
> > On Thu, 10 May 2012 10:07:21 +0200 Lars Schimmer<l.schimmer@cgv.tugraz.at>
> > wrote:
> [...]
> >> mdadm -E tells me e.g. for md1:
> >>
> >> /dev/sdh1:
> >> Events : 206286
> >>
> >> /dev/sdf1:
> >> Events : 206273
> >>
> >> /dev/sdi1:
> >> Events : 197114
> >>
> >> /dev/sdj1:
> >> Events : 206286
> [...]
> >>
> >>
> >> So all 4 disks see some diff state. Any chance on getting raid5
> >> running again and read some data from it?
> >>
> >> Does the mdadm -C --assume-clean option help me in that case anyhow?
> >
> > 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.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-10 10:45 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 [this message]
2012-05-11 10:28 ` John Robinson
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=20120510204516.16571810@notabene.brown \
--to=neilb@suse.de \
--cc=john.robinson@anonymous.org.uk \
--cc=l.schimmer@cgv.tugraz.at \
--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).