From: Neil Brown <neilb@suse.de>
To: Kevin Shanahan <kmshanah@disenchant.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help recovering RAID6 failure
Date: Tue, 16 Dec 2008 10:05:19 +1100 [thread overview]
Message-ID: <18758.58031.230346.101105@notabene.brown> (raw)
In-Reply-To: message from Kevin Shanahan on Tuesday December 16
On Tuesday December 16, kmshanah@disenchant.net wrote:
>
> Oh, and here's what gets added to dmesg after running that command:
>
> raid5: cannot start dirty degraded array for md5
I thought that might be the case. --force is meant to fix that -
remove the 'dirty' flag from the array.
>
> This is run on Linux 2.6.26.9, mdadm 2.6.7.1 (Debian)
Hmm.. and there goes that theory. There was a bug in mdadm prior to
2.6 which caused --force not to work for raid6 with 2 drives missing.
It looks like some of your devices are marks 'clean' and some are
'active'. mdadm is noticing one that is 'clean' and not bothering to
mark the others as 'clean'. The kernel is seeing one that is 'active'
and complaining.
The devices that are 'active' are sd[efl]1. Maybe if you list one of
those last it will work.
e.g.
mdadm -A --force --verbose /dev/md5 /dev/sd[cfghijk]1 /dev/sde1
If not, try listing it first.
I'll try to fix mdadm so that it gets this right.
Thanks,
NeilBrown
next prev parent reply other threads:[~2008-12-15 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 22:03 Help recovering RAID6 failure Kevin Shanahan
2008-12-15 22:15 ` Neil Brown
2008-12-15 22:25 ` Kevin Shanahan
2008-12-15 22:37 ` Kevin Shanahan
2008-12-15 22:39 ` Kevin Shanahan
2008-12-15 23:05 ` Neil Brown [this message]
2008-12-15 23:18 ` Kevin Shanahan
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=18758.58031.230346.101105@notabene.brown \
--to=neilb@suse.de \
--cc=kmshanah@disenchant.net \
--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).