From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Wolfgang Denk <wd@denx.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: Huge values of mismatch_cnt on RAID 6 arrays under Fedora 18
Date: Thu, 31 Jan 2013 18:47:25 +0100 [thread overview]
Message-ID: <20130131174725.GA2441@lazy.lzy> (raw)
In-Reply-To: <20130131121220.F3CA220059E@gemini.denx.de>
On Thu, Jan 31, 2013 at 01:12:20PM +0100, Wolfgang Denk wrote:
> Dear Piergiorgio,
>
> In message <20130129202433.GB7005@lazy.lzy> you wrote:
> >
> > If all error report by raid6check, on the three
> > systems, are "unknown", then it seems to be a
> > software problem.
>
> I think we can be pretty sure of this now. For a test, I installed a
> vanilla mainline Linux kernel (v3.8-rc5) on the affected machines.
>
> A "check" operation showed no more problems, but "raid6test"
> still reported a large number of errors like these:
Hi Wolfgang,
this surprise me quite a lot, the two checks should
have similar results. The only algorithmic difference
I know of is that raid6check reports "per stripe",
while the in kernel check should report "per block".
> ...
> P(4) wrong at 10291
> Q(5) wrong at 10291
> Error detected at 10291: disk slot unknown
> P(3) wrong at 10292
> Q(4) wrong at 10292
> Error detected at 10292: disk slot unknown
> P(2) wrong at 10293
> Q(3) wrong at 10293
> Error detected at 10293: disk slot unknown
> ...
>
> After running a "repair" on the array, both "check" and "raid6test"
> would not report any further issues.
Which is again a surprise, if the repair changed
the parities, then the raid6check should complain,
if before it was not.
This confuses me a lot, I think Neil Brown or
H. Peter Anvin should comment on this situation.
bye.
--
piergiorgio
next prev parent reply other threads:[~2013-01-31 17:47 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 19:26 Huge values of mismatch_cnt on RAID 6 arrays under Fedora 18 Wolfgang Denk
2013-01-27 19:45 ` Chris Murphy
2013-01-27 23:10 ` Wolfgang Denk
2013-01-27 20:05 ` Robin Hill
2013-01-27 23:11 ` Wolfgang Denk
2013-01-28 1:14 ` Phil Turmel
2013-01-28 1:42 ` Chris Murphy
2013-01-28 2:16 ` Chris Murphy
2013-01-28 6:43 ` Wolfgang Denk
2013-01-28 6:36 ` Wolfgang Denk
2013-01-28 7:00 ` Chris Murphy
2013-01-28 10:27 ` Wolfgang Denk
2013-01-28 6:27 ` Wolfgang Denk
2013-01-28 2:07 ` Brad Campbell
2013-01-28 6:39 ` Wolfgang Denk
2013-01-28 7:58 ` Dan Williams
2013-01-28 17:37 ` Piergiorgio Sartor
2013-01-28 18:12 ` Chris Murphy
2013-01-28 19:00 ` Wolfgang Denk
2013-01-28 19:10 ` Wolfgang Denk
2013-01-28 19:22 ` Piergiorgio Sartor
2013-01-28 20:19 ` Wolfgang Denk
2013-01-28 20:44 ` Piergiorgio Sartor
2013-01-28 22:47 ` Chris Murphy
2013-01-28 22:49 ` Chris Murphy
2013-01-28 23:03 ` Wolfgang Denk
2013-01-28 23:13 ` Chris Murphy
2013-01-28 23:31 ` Wolfgang Denk
2013-01-28 22:59 ` Wolfgang Denk
2013-01-28 23:07 ` Chris Murphy
2013-01-28 23:23 ` Wolfgang Denk
2013-01-28 23:42 ` Chris Murphy
2013-01-29 18:02 ` Roy Sigurd Karlsbakk
2013-01-29 18:28 ` Wolfgang Denk
2013-01-29 18:43 ` Roy Sigurd Karlsbakk
2013-01-29 17:49 ` Piergiorgio Sartor
2013-01-29 19:35 ` Paul Menzel
2013-01-29 20:18 ` Piergiorgio Sartor
2013-01-28 23:18 ` Wolfgang Denk
2013-01-29 17:57 ` Piergiorgio Sartor
2013-01-29 18:43 ` Wolfgang Denk
2013-01-29 20:24 ` Piergiorgio Sartor
2013-01-31 12:12 ` Wolfgang Denk
2013-01-31 17:14 ` Chris Murphy
2013-01-31 17:51 ` Piergiorgio Sartor
2013-01-31 18:36 ` Wolfgang Denk
2013-01-31 19:35 ` Chris Murphy
2013-01-31 19:46 ` Chris Murphy
2013-01-31 20:05 ` Wolfgang Denk
2013-01-31 20:41 ` Chris Murphy
2013-01-31 17:47 ` Piergiorgio Sartor [this message]
2013-01-28 19:18 ` Piergiorgio Sartor
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=20130131174725.GA2441@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=linux-raid@vger.kernel.org \
--cc=wd@denx.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 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.