From: Phil Turmel <philip@turmel.org>
To: Wolfgang Denk <wd@denx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Huge values of mismatch_cnt on RAID 6 arrays under Fedora 18
Date: Sun, 27 Jan 2013 20:14:18 -0500 [thread overview]
Message-ID: <5105D0EA.7080100@turmel.org> (raw)
In-Reply-To: <20130127192656.634892005AD@gemini.denx.de>
On 01/27/2013 02:26 PM, Wolfgang Denk wrote:
> I have seen "mismatch_cnt is not 0" warnings in the past, but that has
> always been with RAID 1 arrays, and with relatively small numbers on
> /sys/block/md*/md/mismatch_cnt; my understanding was that this was not
> actually critical.
>
> However, after updating to Fedora 18, I get this message from all
> updated
> systems that have RAID 6 arrays, and with _huge_ numbers of
> mismatch_cnt, like that:
>
> fter updating to Fedora 18, I get this message from all updated
> systems that have RAID 6 arrays, and with _huge_ numbers of
> mismatch_cnt, like that:
>
> # mdadm -q --detail /dev/md0
> /dev/md0:
> Version : 1.2
> Creation Time : Mon Jan 14 14:20:34 2013
Something is missing from this story. Was the original system created
this month, and immediately upgraded? Or was there a "mdadm --create"
in this story you haven't told us about?
> Raid Level : raid6
> Array Size : 1459617792 (1392.00 GiB 1494.65 GB)
> Used Dev Size : 243269632 (232.00 GiB 249.11 GB)
> Raid Devices : 8
> Total Devices : 8
> Persistence : Superblock is persistent
>
> Update Time : Sun Jan 27 02:27:28 2013
> State : clean
> Active Devices : 8
> Working Devices : 8
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 16K
>
> Name : XXX:0 (local to host XXX)
> UUID : da015f96:138b37bf:d5ef71dc:8970ab15
> Events : 8
>
> Number Major Minor RaidDevice State
> 0 8 49 0 active sync /dev/sdd1
> 1 8 65 1 active sync /dev/sde1
> 2 8 81 2 active sync /dev/sdf1
> 3 8 97 3 active sync /dev/sdg1
> 4 8 113 4 active sync /dev/sdh1
> 5 8 129 5 active sync /dev/sdi1
> 6 8 145 6 active sync /dev/sdj1
> 7 8 161 7 active sync /dev/sdk1
> # cat /sys/block/md0/md/mismatch_cnt
> 362732152
>
>
> This is with mdadm v3.2.6 (mdadm-3.2.6-7.fc18.x86_64); except for the
> huge values of mismatch_cnt, I see no other indications for errors on
> the disk drives, RAID arrays or the file systems on top of these.
>
> Is this some known (and hopefully harmless), issue, or must I worry
> about our data?
I would be worried, but there's not enough information here to say.
Please share the output of "mdadm -E /dev/sd[defghijk]1".
Please also explain/share what you've done to conclude the filesystem is
error-free.
Phil
next prev parent reply other threads:[~2013-01-28 1:14 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 [this message]
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
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=5105D0EA.7080100@turmel.org \
--to=philip@turmel.org \
--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.