linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Huge values of mismatch_cnt on RAID 6 arrays under Fedora 18
Date: Tue, 29 Jan 2013 19:43:09 +0100	[thread overview]
Message-ID: <20130129184309.D65DD2A1846@gemini.denx.de> (raw)
In-Reply-To: <20130129175720.GB2396@lazy.lzy>

Dear Piergiorgio,

In message <20130129175720.GB2396@lazy.lzy> you wrote:
>
> my personal opinion would be to confirm
> *all* the data is OK, if you can.

Unfortunately I have no easy way doing this.  Most of the data are
working trees of software builds, or build results, so I have no
checksum or other information.  But all files I accessed so far, of
where I was able to check, were actually correct.

> Uhm, as mentioned, it would be nice to
> find a specific error slot...
> Well, not so nice, but this would point
> to an HW problem.

I am not a friend of quick conclusions in cases like this, but I think
that hardware issues are very unlikely to hit with identical effects
simultaneously on 3 different machines in 2 different locations.


> > OK, add more hardware details...
> > 
> > A: Supermicro X8SAX mainboard, Core i7 CPU 950 @ 3.07GHz, 24 GB RAM
> > H: Supermicro X8ST3 mainboard, Xeon CPU W3565  @ 3.20GHz, 24 GB RAM
> > X: Supermicro X8SAX mainboard, Core i7 CPU 950 @ 3.07GHz, 24 GB RAM
>  
> What does the kernel log says about the choosen
> RAID6 algorithm?

System A:

[   57.121902] raid6: sse2x1    7660 MB/s
[   57.138892] raid6: sse2x2    8687 MB/s
[   57.155890] raid6: sse2x4    9789 MB/s
[   57.155891] raid6: using algorithm sse2x4 (9789 MB/s)
[   57.155892] raid6: using ssse3x2 recovery algorithm

System H:

[   45.360607] raid6: sse2x1    7753 MB/s
[   45.403614] raid6: sse2x2    8777 MB/s
[   45.445612] raid6: sse2x4    9773 MB/s
[   45.472547] raid6: using algorithm sse2x4 (9773 MB/s)
[   45.503347] raid6: using ssse3x2 recovery algorithm

System X:

[   51.471793] raid6: sse2x1    3996 MB/s
[   51.517657] raid6: sse2x2    4851 MB/s
[   51.566579] raid6: sse2x4    4960 MB/s
[   51.598831] raid6: using algorithm sse2x4 (4960 MB/s)
[   51.638697] raid6: using ssse3x2 recovery algorithm


Note: I remembered that I converted yet another machine which has a
(smaller) RAID6 array (4 x SAMSUNG SpinPoint F1 HE502IJ) on a less
powerful PC (Gigabyte P35-DS3R mainboard, Intel Core 2 Duo CPU E6750
@ 2.66GHz, 8 GB RAM).  This shows NO problems (so far).  Here I have:

[   11.253015] raid6: sse2x1    1902 MB/s
[   11.270021] raid6: sse2x2    2296 MB/s
[   11.287274] raid6: sse2x4    3171 MB/s
[   11.287533] raid6: using algorithm sse2x4 (3171 MB/s)
[   11.288127] raid6: using ssse3x2 recovery algorithm


If you can draw any conclusions from that - I can't.

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
GUIs  are  virtually  useless.  Learn  tools.  They're  configurable,
scriptable, automatable, cron-able, interoperable, etc. We don't need
no brain-dead winslurping monolithic claptrap.
                               -- Tom Christiansen in 371140df@csnews

  reply	other threads:[~2013-01-29 18:43 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 [this message]
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
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=20130129184309.D65DD2A1846@gemini.denx.de \
    --to=wd@denx.de \
    --cc=linux-raid@vger.kernel.org \
    --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).