linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "martin f krafft" <madduck@madduck.net>
To: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: what does md do if it finds an inconsistency?
Date: Sun, 6 May 2007 15:36:14 +0200 (CEST)	[thread overview]
Message-ID: <3655.195.137.231.42.1178458574.squirrel@albatross.madduck.net> (raw)
In-Reply-To: <463DB709.8010900@eyal.emu.id.au>

> The first time it reports that it found (and repaired) 128 items.
> It does not mean that you now *have* 128 mismatches.
>
> The next run ('repair' or 'check') will find none (hopefully...)
> and report zero.

Oh, this makes perfect sense, thanks for the explanation.

As the mdadm maintainer for Debian, I would like to come up with a way to
handle mismatches somewhat intelligently. I already have the check
sync_action run once a month on all machines by default (can be turned
on/off via debconf), and now I would like to find a good way to react when
mismatch_count is non-zero. I don't want to write to the components
without the admin's consent though.

Maybe the ideal way would be to have mdadm --monitor send an email on
mismatch_count>0 or a cronjob that regularly sends reminders, until the
admin logs in and runs e.g. /usr/share/mdadm/repairarray.

Thoughts?

Also, if a mismatch is found on a RAID1, how does md decide which copy is
mismatched and which is correct? What about RAID 5/6/10?

Thanks for your time!
-martin

>
> --
> Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
> 	attach .zip as .dat
>
>


  reply	other threads:[~2007-05-06 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06  0:45 what does md do if it finds an inconsistency? martin f krafft
2007-05-06  9:06 ` martin f krafft
2007-05-06 11:07   ` Eyal Lebedinsky
2007-05-06 13:36     ` martin f krafft [this message]
2007-05-06 15:59       ` Gavin McCullagh
2007-05-07  4:08         ` Neil Brown
2007-05-08 13:27       ` Bill Davidsen

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=3655.195.137.231.42.1178458574.squirrel@albatross.madduck.net \
    --to=madduck@madduck.net \
    --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).