From: Michael Evans <mjevans1983@gmail.com>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Sysfs update frequency
Date: Tue, 16 Mar 2010 16:03:08 -0700 [thread overview]
Message-ID: <4877c76c1003161603n26d29db5s2b3d271ca5698ee0@mail.gmail.com> (raw)
In-Reply-To: <150c16851003161525g50e09917rfa9b53be3a500978@mail.gmail.com>
On Tue, Mar 16, 2010 at 3:25 PM, Justin Maggard <jmaggard10@gmail.com> wrote:
> On Tue, Mar 16, 2010 at 2:52 PM, Neil Brown <neilb@suse.de> wrote:
>> On Tue, 16 Mar 2010 14:32:55 -0700
>> Justin Maggard <jmaggard10@gmail.com> wrote:
>>
>>> I've noticed on recent kernels that /sys/block/md?/md/sync_completed
>>> seems to rarely get updated. What is the expected update interval?
>>> For me, it seems to only update about once every 6% or so during the
>>> resync. Of course, /proc/mdstat has the actual current progress.
>>
>> The expected update time is every 6% - actually 1/16 which is 6.25%.
>>
>> sync_completed includes a guarantee that all blocks before this point really
>> have been processed. The number in /proc/mdstat is less precise. The much
>> of the array has been resynced, but due to the possibility of out-of-order
>> completion of writes they may not be a contiguous series of blocks.
>>
>> Providing the guarantee (which is needed for externally-managed metadata)
>> requires briefly stalling the resync, so I didn't want to do it more often.
>> I could possibly make it time-bases instead of size-based though.
>>
>> Is this a problem for you?
>>
>
> Thanks for the info. No, it's not much of a problem, really. Just
> seemed strange that an array of 2TB disks could resync for an hour
> with no update to sync_completed. I thought I remembered older
> kernels updating a lot more frequently, but I could be wrong about
> that. So I take it that point is where the resync would resume if the
> system was rebooted?
>
> -Justin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Rather than a time basis would it be possible to have a sysfs
paramater which could be tuned via write?
Candidates for this would be something like:
sync_flushes_per_action (fractional unit, every 1/N of the device)
OR
sync_flush_stripes
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-16 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 21:32 Sysfs update frequency Justin Maggard
2010-03-16 21:52 ` Neil Brown
2010-03-16 22:25 ` Justin Maggard
2010-03-16 23:03 ` Michael Evans [this message]
2010-03-20 16:48 ` Bill Davidsen
2010-03-23 3:22 ` Neil Brown
2010-03-24 19:49 ` 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=4877c76c1003161603n26d29db5s2b3d271ca5698ee0@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=jmaggard10@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).