From: John Robinson <john.robinson@anonymous.org.uk>
To: Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Internal bitmap always 1/1
Date: Tue, 04 Jan 2011 17:20:04 +0000 [thread overview]
Message-ID: <4D2356C4.2010004@anonymous.org.uk> (raw)
In-Reply-To: <AANLkTin_HZkgTb16Vzwvg93V9P6nm_dM-ZrjUnsKCEk-@mail.gmail.com>
On 04/01/2011 16:51, Andrea Gelmini wrote:
> Hi all,
> and thanks a lot for your effort on MdAdm.
> With latest git version of mdadm tools¹ I have
> problems with creation of internal bitmap. Doing something like this:
> ./mdadm -Ss;./mdadm --create /dev/md0 --level=1 --raid-devices=2
> --assume-clean --bitmap=internal /dev/sdb5 missing --auto=md -e
> 1.2;cat /proc/mdstat
> mdadm: stopped /dev/md0
> mdadm: /dev/sdb5 appears to be part of a raid array:
> level=raid1 devices=2 ctime=Tue Jan 4 17:29:06 2011
> Continue creating array? y
> mdadm: array /dev/md0 started.
> Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
> md0 : active raid1 sdb5[0]
> 55777208 blocks super 1.2 [2/1] [U_]
> bitmap: 1/1 pages [4KB], 65536KB chunk
>
> I always have 1/1 pages (also with different partition sizes: 1G
> as 80G, no differences).
Why is this a problem? Your bitmap is simply too small to need more than
one page, whether it's a 1G or 80G. With a 16MB bitmap chunk size on a
2TB array I have 2 pages.
If you want to see how busy the bitmap is, try `mdadm --examine-bitmap
/dev/component`
Cheers,
John.
--
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:[~2011-01-04 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 16:51 Internal bitmap always 1/1 Andrea Gelmini
2011-01-04 17:20 ` John Robinson [this message]
2011-01-04 20:28 ` NeilBrown
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=4D2356C4.2010004@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=andrea.gelmini@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).