From: John Robinson <john.robinson@anonymous.org.uk>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: bitmap questions
Date: Thu, 14 Oct 2010 13:11:10 +0100 [thread overview]
Message-ID: <4CB6F35E.6040307@anonymous.org.uk> (raw)
In-Reply-To: <201010140800.38419.a.miskiewicz@gmail.com>
On 14/10/2010 07:00, Arkadiusz Miskiewicz wrote:
[...]
> So there is no way to know in advance how much is going to be resynced when
> sudden reset would happen in that moment?
Only in the general sense that there's a limit to how many chunks could
have been dirtied in whatever period your kernel will hang on to stuff
before insisting on flushing it. I think that defaults to 5 seconds, so
you'd have to have a pathological workload to dirty so many chunks the
resync might take more than a minute.
Cheers,
John.
next prev parent reply other threads:[~2010-10-14 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 16:24 bitmap questions Arkadiusz Miskiewicz
2010-10-14 5:02 ` Paul Clements
2010-10-14 6:00 ` Arkadiusz Miskiewicz
2010-10-14 12:11 ` John Robinson [this message]
2010-10-14 12:39 ` Mario 'BitKoenig' Holbe
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=4CB6F35E.6040307@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=a.miskiewicz@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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).