All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjammin2068 <benjammin2068@gmail.com>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: WARNING: mismatch_cnt is not 0 on <array device>
Date: Wed, 28 Sep 2016 10:55:06 -0500	[thread overview]
Message-ID: <b87f3f0d-e9a9-8ece-d708-9b8730157bfb@gmail.com> (raw)
In-Reply-To: <be044941-8097-7d6f-5216-294fe2cac4d9@websitemanagers.com.au>

On 09/27/2016 06:09 PM, Adam Goryachev wrote:
> Just out of interest, but I'm not sure how useful your munin monitoring will be... AFAIK, the mismatch_cnt value is only updated when you run a check, which would probably take some number of hours to complete. I would guess that you are unlikely to run more than one check a week or month.... and as soon as there is any change (unless you know the explanation) then you should be looking to resolve that.
>
> Unless of course I'm wrong about when the count is updated?

You would be correct - only during checks - but it's an easy way for me to just keep track of it..

And a check takes about 3hrs on this array. (and it happens every weekend)

 -Ben

  reply	other threads:[~2016-09-28 15:55 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
2016-09-27 23:09                 ` Adam Goryachev
2016-09-28 15:55                   ` Benjammin2068 [this message]
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=b87f3f0d-e9a9-8ece-d708-9b8730157bfb@gmail.com \
    --to=benjammin2068@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mailinglists@websitemanagers.com.au \
    /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.