From: Benjammin2068 <benjammin2068@gmail.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: WARNING: mismatch_cnt is not 0 on <array device>
Date: Tue, 27 Sep 2016 11:27:13 -0500 [thread overview]
Message-ID: <41c176d2-0235-6ff0-996c-b32dc95d487d@gmail.com> (raw)
In-Reply-To: <27577b8a-1b63-8f1a-9b68-b056622a5268@fnarfbargle.com>
On 09/27/2016 04:16 AM, Brad Campbell wrote:
> On 27/09/16 09:08, Benjammin2068 wrote:
>>
>
>> Also, I just did a "repair" and the mismatch is now back to 8... which seems like a suspicious number considering the filesystem on this new drive (because it's a WD10 series with 4096byte sectors) has a slightly larger FS than the Samsung HD103SJ (and Seagate equivalents) in the array too.
>
> See that is a bad thing to do if you even remotely suspect you have a problem. All a "repair" does is check the parity on a stripe and if there is a mismatch it re-writes it. You are writing to an array that apparently has issues.
>
> I'd be checking the filesystem and file contents very carefully for corruption, and running several sequential check actions to keep an eye on the mismatch count.
>
Yep.
Once I reconfig'd the hardware and checked the cables in the system on boot the number is now 0. (which makes sense at boot - but is creepy) I put a monitor into munin which I'll be watching closely for when it changes.
BUT... I think I did find the problem. The card was running hot due to airflow. That's been remedied (I hope) -- the temp sensor on the heat-sink for the PCIe controller now sits around 45'C which is fine. Before it was >= 60'C . :O
Thanks again everyone,
-Ben
p.s. The Linux RAID Wiki doesn't cover mismatch_cnt at all.... would be kinda nice considering how critical (or not) this is... and what to do about it.
next prev parent reply other threads:[~2016-09-27 16:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 2:43 WARNING: mismatch_cnt is not 0 on <array device> Benjammin2068
2016-09-26 3:42 ` 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 [this message]
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=41c176d2-0235-6ff0-996c-b32dc95d487d@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 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).