linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: NeilBrown <neilb@suse.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
	linux-raid@vger.kernel.org
Subject: Re: Reliability of bitmapped resync
Date: Mon, 23 Feb 2009 21:19:05 +0100	[thread overview]
Message-ID: <20090223201905.GA7585@lazy.lzy> (raw)
In-Reply-To: <b2460d0414270e6a6be4c91ec2d5a071.squirrel@neil.brown.name>

Hi,

> What exactly do you mean by "check".
> 
> If you mean "look in /sys/block/md0/md/mismatch_cnt", then that is
> exactly what I would expect.  The resync found some differences, just
> as you would expect it to, and reported them.
> 
> However if by "check" you mean:
>   echo check > /sys/block/md0/md/sync_action
>   mdadm --wait /dev/md0
>   cat /sys/block/md0/md/mismatch_cnt

yes, that is what I mean.
I start the check _after_ the resync.

Actually, maybe this is not correct, I keep running
something like:

watch cat /proc/mdstat /sys/block/md2/md/mismatch_cnt

So I can see real-time, so to speak, the check
progress and the mismatch count, just to have
an idea on where, on the RAID, the mismatches
could be located. 

Is this a problem?

> then I would not expect any mismatches, and the resync should have
> fixed them.
> 
> If it is the later, that is a real concern and I will need to look into it.
> Please let me know exactly which kernel version and mdadm version you
> are running.

It is an up-to-date Fedora 10, i.e. kernel-2.6.27.15-170.2.24.fc10
and mdadm-2.6.7.1-1.fc10.

Thanks again,

bye,

-- 

piergiorgio

  reply	other threads:[~2009-02-23 20:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 19:40 Reliability of bitmapped resync Piergiorgio Sartor
2009-02-23 19:59 ` NeilBrown
2009-02-23 20:19   ` Piergiorgio Sartor [this message]
2009-02-23 21:31     ` NeilBrown
2009-02-23 21:40       ` Piergiorgio Sartor
2009-02-23 21:49         ` NeilBrown
2009-02-24 19:39           ` Piergiorgio Sartor
2009-02-25  2:39             ` Neil Brown
2009-02-25 18:51               ` Piergiorgio Sartor
2009-03-13 17:19               ` Bill Davidsen
2009-02-23 21:18   ` Eyal Lebedinsky
2009-02-23 21:36     ` Piergiorgio Sartor

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=20090223201905.GA7585@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).