linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Benjammin2068 <benjammin2068@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: WARNING: mismatch_cnt is not 0 on <array device>
Date: Tue, 27 Sep 2016 21:36:24 +0500	[thread overview]
Message-ID: <20160927213624.739f80ba@natsu> (raw)
In-Reply-To: <41c176d2-0235-6ff0-996c-b32dc95d487d@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

On Tue, 27 Sep 2016 11:27:13 -0500
Benjammin2068 <benjammin2068@gmail.com> wrote:

> 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

I wouldn't trust such controller anyway. 15 degrees difference and it
(allegedly) gives you silent data corruption? What if you have a particularly
hot day, and/or the AC is out for a few hours.
There is a lot of better failure modes than this (honestly reported read or
CRC errors for a start, or heck, even complete lock-up of the controller would
be more preferrable).

-- 
With respect,
Roman

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-09-27 16:36 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
2016-09-27 16:36             ` Roman Mamedov [this message]
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=20160927213624.739f80ba@natsu \
    --to=rm@romanrm.net \
    --cc=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).