linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jack Wang <xjtuwjp@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [RFC] md raid resync counter
Date: Tue, 05 Nov 2013 10:16:56 +0100	[thread overview]
Message-ID: <5278B788.5030304@gmail.com> (raw)
In-Reply-To: <20131105161255.130a9c52@notabene.brown>

On 11/05/2013 06:12 AM, NeilBrown wrote:
> On Mon, 04 Nov 2013 10:26:42 +0100 Jack Wang <xjtuwjp@gmail.com> wrote:
> 
>> On 11/02/2013 12:48 AM, NeilBrown wrote:
>>> On Fri, 01 Nov 2013 13:59:40 +0100 Jack Wang <xjtuwjp@gmail.com> wrote:
>>>
>>>> Hi Neil and all,
>>>>
>>>> Is there anyway to know:
>>>>
>>>> 1. How often does a raid start to resync?
>>>
>>> Look at your logs?
>>>
>>>> 2. How many bytes did it resync?
>>>
>>> Look at "mismatch_cnt" in sysfs (and multiply by 512).
>>>
>>> NeilBrown
>>>
>>>
>> Thanks Neil,
>>
>> You're always very helpful :)
>>
>> About the second one. As I checked in my system kernel 3.4.51
>>
>> when raid is resync:
>> cat /proc/mdstat
>> Personalities : [raid1]
>> md1 : active raid1 dm-1[3] dm-2[2]
>>       23762944 blocks super 1.2 [2/1] [_U]
>>       [==>..................]  recovery = 10.7% (2562240/23762944)
>> finish=7.5min speed=46565K/sec
> 
> This array is doing "recovery", not "resync".
> 
> "Resync" is when the devices should all contains the same data but maybe
> don't due to some  error.  So md/raid1 checks and fixes the errors.
> "recovery" is when a spare has been added and data is being copied  onto it.
> 
> 
>> # cat /sys/block/md1/md/mismatch_cnt
>> 0
>>
>> cat /sys/block/md1/md/degraded
>> 1
>>  cat /sys/block/md1/md/mismatch_cnt
>> 0
>> # cat /sys/block/md1/md/sync_completed
>> 8911488 / 47525888
>>
>> mismatch_cnt is 0, sync_completed look what I want?
> 
> "sync_completed" is a number which is somewhat smaller than the number of
> sectors that have been be processed by the current
> sync/repair/recover/whatever.
> 
> Slightly smaller because it is only updated occasionally.
> 
> I don't really know what you want because you didn't say what you would do
> with the information, but it is possible that this is what you want.

Thanks Neil for clarification.
I think we need track both recovery and resync status, mismatch_cnt and
sync_completed are what we want.

Regards,
Jack
> 
> 
>>
>> Jack
> 
> 
> NeilBrown
> 


      reply	other threads:[~2013-11-05  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 12:59 [RFC] md raid resync counter Jack Wang
2013-11-01 23:48 ` NeilBrown
2013-11-04  9:26   ` Jack Wang
2013-11-05  5:12     ` NeilBrown
2013-11-05  9:16       ` Jack Wang [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=5278B788.5030304@gmail.com \
    --to=xjtuwjp@gmail.com \
    --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).