From: NeilBrown <neilb@suse.de>
To: Martin Ziler <martin.ziler@googlemail.com>
Cc: linux RAID <linux-raid@vger.kernel.org>
Subject: Re: degraded raid 6 (1 bad drive) showing up inactive, only spares
Date: Thu, 21 Jun 2012 07:56:49 +1000 [thread overview]
Message-ID: <20120621075649.06cd9631@notabene.brown> (raw)
In-Reply-To: <F137B54C-A982-4EBC-A04B-5C47CA07BE12@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
On Sun, 17 Jun 2012 17:52:07 +0200 Martin Ziler <martin.ziler@googlemail.com>
wrote:
> Hello everybody,
>
> long time no seen. As I was unable to find a permutation that would result in an fsck-output that looks ok I generated the 360.000 permutations using Neil's shell script. I then composed a little script that would try a permutation, do the fsck, stop the raid an go on with the new possibility and inserted the fsck-output into a text-file. The whole 360.000 permutations just recently finished - after some 6 days of building and fscking. I have not yet analyzed the output. I did however search for the term "clean" as a positive result would possibly contain that term.
>
> I got 711 different drive-combinations that will result in this: /dev/md0: clean, 204968/849158144 files, 3394436623/3396621312 blocks.
>
> If there really is only one working drive order, I guess I am pretty much doomed. I do hope I'll be able to rule out a large portion of those results before going into some more detail. I did get it correct, though, that there is only one possible order resulting in a working array? I gotta figure out how to analyze the output file now. It's 125 MB. I guess I'll probably split it and load it into my spreadsheet. In one go I'd stumble across the 1.000.000 row-limit.
>
> regards,
>
> Martin
Yes, there is only one correct order.
711 is very close to 720 which is 6! I wonder if that is significant.
Maybe you need "fsck -n -f" to force it to do a more thorough check even
though the fs appears to be clean.
If you "echo check > /sys/block/mdXX/md/sync_action", wait 30 seconds or so,
then "echo idle > ......", then check "mismatch_cnt", the correct ordering
should have a significantly lower number - probably zero.
Other orders will have a high number.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-06-20 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 15:52 degraded raid 6 (1 bad drive) showing up inactive, only spares Martin Ziler
2012-06-20 21:56 ` NeilBrown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-07 11:55 Martin Ziler
2012-06-07 12:29 ` NeilBrown
[not found] ` <CAGHsWsm_Xvf59VCuHyJvoMW6peiFHK=YQKGzr3cq=RDk7jyqKg@mail.gmail.com>
2012-06-07 21:14 ` NeilBrown
[not found] ` <C9680CD3-8DA8-4FE3-8337-481676213C39@googlemail.com>
2012-06-09 22:09 ` NeilBrown
2012-06-07 21:16 ` Oliver Schinagl
2012-06-07 22:34 ` NeilBrown
[not found] ` <alpine.DEB.2.00.1206080743310.25054@uplift.swm.pp.se>
2012-06-15 7:37 ` NeilBrown
2012-06-15 11:35 ` Oliver Schinagl
2012-06-15 12:37 ` NeilBrown
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=20120621075649.06cd9631@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=martin.ziler@googlemail.com \
/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).