From: Peter Rabbitson <rabbit+list@rabbit.us>
To: Ty! Boyack <ty@nrel.colostate.edu>
Cc: Markus Hochholdinger <Markus@hochholdinger.net>,
linux-raid@vger.kernel.org
Subject: Re: Is it possilble to be "delay tolerant" or have "slow dropout" of unavailable components?
Date: Tue, 08 Apr 2008 20:54:12 +0200 [thread overview]
Message-ID: <47FBBF54.4090609@rabbit.us> (raw)
In-Reply-To: <47FBB842.2030902@nrel.colostate.edu>
Ty! Boyack wrote:
>
> <snip>
>
> Right now, without the automation, it is possible, and likely, that an
> operator cannot respond in time to avoid having the bitmap fill up, and
> then we are into a long resync.
The bitmap can not "fill-up" - this is by design. It is created by simply
subdividing the _entire_ array into a number of equally sized regions (the
exact amount depends on the bitmap size, and the size of every region depends
on the md device size). Then any time a write operation touches the disk the
corresponding region is marked as dirty. There might be one write or a
thousand writes - as long as they all fall within the same region - it is the
only one which will be resync-ed.
HTH
Peter
prev parent reply other threads:[~2008-04-08 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 16:56 Is it possilble to be "delay tolerant" or have "slow dropout" of unavailable components? Ty! Boyack
2008-04-08 17:48 ` Markus Hochholdinger
2008-04-08 18:24 ` Ty! Boyack
2008-04-08 18:54 ` Peter Rabbitson [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=47FBBF54.4090609@rabbit.us \
--to=rabbit+list@rabbit.us \
--cc=Markus@hochholdinger.net \
--cc=linux-raid@vger.kernel.org \
--cc=ty@nrel.colostate.edu \
/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).