linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: "Роман Алексеев" <r.alekseev@qwarta.ru>
Cc: linux-raid@vger.kernel.org
Subject: Re: Optimal value for bitmap-chunk option
Date: Wed, 19 Jun 2013 10:38:38 +0600	[thread overview]
Message-ID: <20130619103838.7c3fb6e0@natsu> (raw)
In-Reply-To: <51C057F9.3020005@qwarta.ru>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

On Tue, 18 Jun 2013 16:52:09 +0400
Роман Алексеев  <r.alekseev@qwarta.ru> wrote:

> Hello,
> 
> I want to speed up rebuilding process of the raid to do that I'm going
> to apply the command:
> 
> mdadm --grow --bitmap=internal --bitmap-chunk=NNNN /dev/mdX
> 
> But I don't know how to calculate optimal value of bitmap-chunk option.
> How can I do that?

It's just the minimum granularity of pieces that get rebuilt after unclean
shutdowns. E.g. if your array decides it's "dirty" in 5 different areas, with
a 16MB chunk the rebuild will process 5*16MB, but with a 128MB it will rebuild
5*128MB. On modern systems the difference in time required to do the rebuild
between these two will be negligible. But having a larger size helps
noticeably in everyday operation (makes writes faster). So there is nothing to
"calculate" really, just use a reasonably large size like 128 or 256 MB.

https://raid.wiki.kernel.org/index.php/Write-intent_bitmap
http://techblog.tgharold.com/2013/01/mdadm-using-bitmaps-to-speed-up-rebuilds.html
http://blog.liw.fi/posts/write-intent-bitmaps/ (the 1st comment)

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2013-06-19  4:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 12:52 Optimal value for bitmap-chunk option Роман Алексеев
2013-06-19  4:38 ` Roman Mamedov [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=20130619103838.7c3fb6e0@natsu \
    --to=rm@romanrm.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=r.alekseev@qwarta.ru \
    /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).