linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Chris Murphy <lists@colorremedies.com>
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 19:36:06 +0100	[thread overview]
Message-ID: <20130131183606.E4C23200276@gemini.denx.de> (raw)
In-Reply-To: <3DB28596-B1D6-48A9-9520-4CF9D367E39D@colorremedies.com>

Dear Chris Murphy,

In message <3DB28596-B1D6-48A9-9520-4CF9D367E39D@colorremedies.com> you wrote:
> 
> > After running a "repair" on the array, both "check" and "raid6test"
> > would not report any further issues.
> 
> Yes but this would be consistent with a derivative parity, written
> to disk and then checked against an algorithm that expects derivative
> parity. What happens if you go back to the old kernel before all the
> problems were happening and you do a check? What happens if you go
> back to a Fedora kernel you know exhibited the problem and you do a
> check?

I cannot test the exact old kernel I was running before any more;
Fedora has released an update in the meantime, and they do not keep
older updates around, only the very latest one - which is the same
version as causes the problems.  When using the (really old) kernel
from the installation media, I see the same behaviour as with current
mainline: I have to run a "repair", and then the array is, and
remains, clean.

With the current Fedora kernel, the first check will report errors
which do not go away permanently, not even with a "repair".

> Question for Piergiorgio is if check and raid6test use the same, or
> independent, code for checking parity?

My impression is that they must use different code - raid6test takes
much, much longer and causes a much higher CPU load than running
"check".

> I think a bug needs to be filed with the information you have thus far.

I did this, actually in parallel with reporting the issues here:
https://bugzilla.redhat.com/show_bug.cgi?id=904831

I think the relevant Fedora people are on Cc:, but there was zero
response so far; seems potential data loss is of no concern to the
Fedora project :-(

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
You don't have to worry about me. I might have been born yesterday...
but I stayed up all night.

  parent reply	other threads:[~2013-01-31 18:36 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 [this message]
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
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=20130131183606.E4C23200276@gemini.denx.de \
    --to=wd@denx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=piergiorgio.sartor@nexgo.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 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).