From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
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: Sun, 06 May 2007 21:07:53 +1000 [thread overview]
Message-ID: <463DB709.8010900@eyal.emu.id.au> (raw)
In-Reply-To: <20070506090642.GA22083@lapse.madduck.net>
martin f krafft wrote:
> also sprach martin f krafft <madduck@madduck.net> [2007.05.06.0245 +0200]:
>
>>With the check feature of the recent md feature, the question popped
>>up what happens when an inconsistency is found. Does it fix it? If
>>so, which disk it assumes to be wrong if an inconsistency is found?
>
>
> What I meant was of course
>
> echo repair > sycn_action
>
> I am unsure what happens:
>
> piper:/sys/block/md7/md# cat mismatch_cnt
> 128
> piper:/sys/block/md7/md# echo repair > sync_action
> piper:/sys/block/md7/md# cat sync_action
> idle
> piper:/sys/block/md7/md# cat mismatch_cnt
> 128
>
> If I do this again, then mismatch_cnt goes to 0. Not the first time.
>
> md7 : active raid10 sda2[0] sdc2[2] sdb2[1]
> 1373376 blocks 64K chunks 2 near-copies [3/3] [UUU]
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.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
attach .zip as .dat
next prev parent reply other threads:[~2007-05-06 11:07 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 [this message]
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
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=463DB709.8010900@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--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).