From: NeilBrown <neilb@suse.de>
To: Fabian Knorr <knorrfab@fim.uni-passau.de>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: Recovering an Array with inconsistent Superblocks
Date: Sun, 5 Jan 2014 20:56:12 +1100 [thread overview]
Message-ID: <20140105205612.093276ef@notabene.brown> (raw)
In-Reply-To: <1388912870.3591.4.camel@vessel>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
On Sun, 05 Jan 2014 10:07:50 +0100 Fabian Knorr <knorrfab@fim.uni-passau.de>
wrote:
> > Try this:
> >
> > mdadm --stop /dev/md0
> >
> > mdadm -Afv /dev/md0 /dev/sd[bcefghi]1
> >
> > It leaves out /dev/sda, which appears to have been the spare in the
> > original setup.
> >
> > If MD is happy after that, use fsck -n on your logical volumes to verify
> > your FS integrity, and/or see the extent of the damage (little or none,
> > I think).
>
> This had the same result as simply trying --assemble --scan, see
> "assemble.log". I tried using sda1 instead of sdb1 as well as the both
> seem to have ID 4 ("assemble2.log"), same thing again.
>
> Do you have any idea why mdadm seems to ignore --force and does not add
> the outdated disks? (Or am I misinterpreting --force?)
I haven't read the whole thread, but this sounds like the bug fixed by:
commit f81a2b56c4b437f66aaf5582a9c6b7f5ab2103c4
Author: NeilBrown <neilb@suse.de>
Date: Tue Oct 22 09:55:04 2013 +1100
Assembe: fix bug in force_array - it wasn't forcing properly.
try getting mdadm from git and building that
git clone git://neil.brown.name/mdadm
cd mdadm
make
NeilBrown
>
> Thanks.
>
> Fabian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-01-05 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 10:04 Recovering an Array with inconsistent Superblocks Fabian Knorr
2014-01-04 16:24 ` Phil Turmel
2014-01-04 17:59 ` Can Jeuleers
2014-01-04 19:16 ` Phil Turmel
2014-01-04 22:05 ` Fabian Knorr
2014-01-05 2:32 ` Phil Turmel
2014-01-05 9:07 ` Fabian Knorr
2014-01-05 9:56 ` NeilBrown [this message]
2014-01-05 10:40 ` Fabian Knorr
[not found] ` <1388918703.3591.20.camel@vessel>
2014-01-05 18:25 ` Phil Turmel
2014-01-05 23:50 ` NeilBrown
2014-01-06 14:00 ` Fabian Knorr
2014-01-07 0:26 ` NeilBrown
2014-01-14 8:54 ` David Brown
2014-01-04 22:08 ` Fabian Knorr
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=20140105205612.093276ef@notabene.brown \
--to=neilb@suse.de \
--cc=knorrfab@fim.uni-passau.de \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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.