From: Bill Davidsen <davidsen@tmr.com>
To: martin f krafft <madduck@madduck.net>
Cc: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: what does md do if it finds an inconsistency?
Date: Tue, 08 May 2007 09:27:53 -0400 [thread overview]
Message-ID: <46407AD9.1060400@tmr.com> (raw)
In-Reply-To: <3655.195.137.231.42.1178458574.squirrel@albatross.madduck.net>
martin f krafft wrote:
>> 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.
>
That sounds right. Some arrarys have persistent mismatches if they are
in use, you are unlikely to want to even attempt to take corrective
action. You might want to have a config file and just run a program
which reads the config regularly and acts based on what it finds.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-05-08 13:27 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
2007-05-06 15:59 ` Gavin McCullagh
2007-05-07 4:08 ` Neil Brown
2007-05-08 13:27 ` Bill Davidsen [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=46407AD9.1060400@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=madduck@madduck.net \
/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).