All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Benjammin2068 <benjammin2068@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: WARNING: mismatch_cnt is not 0 on <array device>
Date: Tue, 27 Sep 2016 20:35:00 +0100	[thread overview]
Message-ID: <57EAC9E4.2000109@youngman.org.uk> (raw)
In-Reply-To: <5427ce35-f222-8a2c-486e-441c4c6ec9a6@gmail.com>

On 27/09/16 18:30, Benjammin2068 wrote:
> I have smartctl running for all my drives -- but that doesn't help me at the mdadm level.
> 
> While you're in the docs adding stuff about mismatch_cnt, is there anything that can help someone backtrace which block cause the count to go up? This would help us mere mortals maybe go back to inspect a block or a file or something to make sure it's not corrupted.

I'm planning to go back through the archives as best I can (I keep a
local archive :-), and I'm starring everything of interest. So if
anybody can chime in, I'll make a note! :-)

All this should eventually get there ... and I'm planning to add a
kernel programming section too - not least because I want to do some!

Cheers,
Wol

  reply	other threads:[~2016-09-27 19:35 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
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 [this message]
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=57EAC9E4.2000109@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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 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.