From: NeilBrown <neilb@suse.de>
To: Jack Wang <xjtuwjp@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [RFC] md raid resync counter
Date: Sat, 2 Nov 2013 10:48:08 +1100 [thread overview]
Message-ID: <20131102104808.47834bdc@notabene.brown> (raw)
In-Reply-To: <5273A5BC.5060109@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
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
>
> If not, for the first one, I think we cound add field into mddev like
> resync_counter, increase when resync done, and annother field into
> md_rdev to track how many bytes synced to the outdated disk?
>
> Regards,
> Jack
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-11-01 23:48 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 [this message]
2013-11-04 9:26 ` Jack Wang
2013-11-05 5:12 ` NeilBrown
2013-11-05 9:16 ` Jack Wang
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=20131102104808.47834bdc@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=xjtuwjp@gmail.com \
/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).