From: Benjammin2068 <benjammin2068@gmail.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: WARNING: mismatch_cnt is not 0 on <array device>
Date: Sun, 25 Sep 2016 21:43:30 -0500 [thread overview]
Message-ID: <26b91420-97c9-f405-aa71-16cd5cda3a67@gmail.com> (raw)
Hey all,
So the RAID5 which I upgraded to RAID6 was humming along all week just fine (I did the change last weekend) and this weekend I got this:
WARNING: mismatch_cnt is not 0 on /dev/md127
The array seems happy and clean:
> /dev/md127:
> Version : 1.2
> Creation Time : Tue Aug 23 03:06:46 2011
> Raid Level : raid6
> Array Size : 2930276352 (2794.53 GiB 3000.60 GB)
> Used Dev Size : 976758784 (931.51 GiB 1000.20 GB)
> Raid Devices : 5
> Total Devices : 6
> Persistence : Superblock is persistent
>
> Intent Bitmap : Internal
>
> Update Time : Sun Sep 25 21:42:55 2016
> State : clean
> Active Devices : 5
> Working Devices : 6
> Failed Devices : 0
> Spare Devices : 1
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Name : :BigRAID
> UUID : 97b17840:3eaff079:d8e384d0:bfdbda42
> Events : 905701
>
> Number Major Minor RaidDevice State
> 6 8 81 0 active sync /dev/sdf1
> 1 8 33 1 active sync /dev/sdc1
> 5 8 49 2 active sync /dev/sdd1
> 4 8 65 3 active sync /dev/sde1
> 8 8 97 4 active sync /dev/sdg1
>
> 7 8 113 - spare /dev/sdh1
I don't think I've ever got a message before about mismatch_cnt
-Ben
next reply other threads:[~2016-09-26 2:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 2:43 Benjammin2068 [this message]
2016-09-26 3:42 ` WARNING: mismatch_cnt is not 0 on <array device> Brad Campbell
2016-09-26 7:19 ` Benjammin2068
2016-09-26 7:40 ` Brad Campbell
2016-09-26 19:47 ` Benjammin2068
2016-09-26 21:15 ` Phil Turmel
2016-09-27 1:08 ` Benjammin2068
2016-09-27 9:16 ` Brad Campbell
2016-09-27 16:27 ` Benjammin2068
2016-09-27 16:36 ` Roman Mamedov
2016-09-27 17:24 ` Benjammin2068
2016-09-27 16:45 ` Wols Lists
2016-09-27 17:30 ` Benjammin2068
2016-09-27 19:35 ` Wols Lists
2016-09-27 23:09 ` Adam Goryachev
2016-09-28 15:55 ` Benjammin2068
2016-10-02 17:33 ` Benjammin2068
[not found] ` <0f6bd6f6-20ee-1720-23fc-27d206063bfc@gmail.com>
2016-11-08 19:52 ` Benjammin2068
2016-11-08 19:53 ` Benjammin2068
2016-11-08 20:38 ` Phil Turmel
2016-11-08 21:01 ` Wols Lists
2016-11-09 19:00 ` Benjammin2068
2017-02-28 19:50 ` WARNING: mismatch_cnt is not 0 on <array device> [SOLVED?] Benjammin2068
2016-11-09 19:00 ` WARNING: mismatch_cnt is not 0 on <array device> Benjammin2068
2016-11-09 19:52 ` Benjammin2068
2016-09-27 6:42 ` Benjammin2068
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=26b91420-97c9-f405-aa71-16cd5cda3a67@gmail.com \
--to=benjammin2068@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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.