linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: 658701@bugs.debian.org, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Bug#658701: mdadm: should send email if mismatches are reported by a check
Date: Mon, 28 May 2012 11:41:30 +1000	[thread overview]
Message-ID: <20120528114130.31b6c1db@notabene.brown> (raw)
In-Reply-To: <4FC0EB0C.1080800@msgid.tls.msk.ru>

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

On Sat, 26 May 2012 18:39:08 +0400 Michael Tokarev <mjt@tls.msk.ru> wrote:

> Neil, can you comment on the change to Monitor offered
> in the mentioned bugreport please?
> 
> On 12.04.2012 23:28, Michael Tokarev wrote:
> > Neil, re http://bugs.debian.org/658701 , how do you think,
> > is it okay if mdadm --monitor will send email in case check
> > found mismatches, the same way it sends email about other
> > more critical errors?
> > 
> > I think Russell has a good point here, but there's one more
> > source of mismatches we have in kernel - some "sporadic"
> > mismatches in raid1 and raid10, especially when these are
> > used as swap space...
> > 
> > In Debian we've several bugreports already requesting more
> > attention to mismatch_cnt, see:
> > 
> >  http://bugs.debian.org/658701 (this one)
> >  http://bugs.debian.org/599821
> >  http://bugs.debian.org/588516
> > 
> > Thank you!
> > 
> > /mjt

Sorry for not replying the first time :-(

I do not agree with the suggested change to mdadm.
A non-zero mismatch count may not be a problem.
It could be due to swap writing to a RAID1/RAID10.
It could also be due to a RAID1/RAID10/RAID6 having been
created with --assume-clean.  This is perfectly safe thing
to do but results in a non-zero mismatch_cnt.

mdadm --monitor will run a program on every event.  If someone
wants more events reported than currently are reported, they are
free to write a script to do whatever they like.

If md finds unreadable blocks and fixes them, then that certainly
might be interesting.  However that is interesting much more broadly than
just for md, and I believe 'smart' makes that information available.  So
having it reported from SMART would be more sensible.

In brief: mismatch_cnt maybe useful to someone who understands what is means
and is investigating some issues, but it is not something that should be
automatically reported to a casual sysadmin.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-05-28  1:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120205123450.21371.88843.reportbug@xev>
     [not found] ` <4F2E90AD.3020405@msgid.tls.msk.ru>
2012-04-12 19:28   ` Bug#658701: mdadm: should send email if mismatches are reported by a check Michael Tokarev
2012-05-26 14:39     ` Michael Tokarev
2012-05-28  1:41       ` NeilBrown [this message]

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=20120528114130.31b6c1db@notabene.brown \
    --to=neilb@suse.de \
    --cc=658701@bugs.debian.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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).