From: John Robinson <john.robinson@anonymous.org.uk>
To: Paul Clements <paul.clements@us.sios.com>
Cc: CoolCold <coolthecold@gmail.com>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: possible bug - bitmap dirty pages status
Date: Wed, 31 Aug 2011 13:56:29 +0100 [thread overview]
Message-ID: <4E5E2F7D.1010306@anonymous.org.uk> (raw)
In-Reply-To: <CAECXXi5eo3J8PPXP5xTm-PrqazC_fkwNnjtiAGM4NtsGBMahHA@mail.gmail.com>
On 31/08/2011 13:30, Paul Clements wrote:
> On Wed, Aug 31, 2011 at 5:05 AM, CoolCold<coolthecold@gmail.com> wrote:
>
>>> root@gamma2:~# cat /proc/mdstat
>>> Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
>>> md3 : active raid1 sdc3[1] sdb3[0]
>>> 1443552640 blocks [2/2] [UU]
>>> bitmap: 16/22 pages [64KB], 32768KB chunk
>
>> More details now:
>> Array still has 16/22 dirty pages:
>
>> root@gamma2:~# mdadm --examine-bitmap /dev/sdc3
>
>> Sync Size : 1443552640 (1376.68 GiB 1478.20 GB)
>> Bitmap : 44054 bits (chunks), 189 dirty (0.4%)
>
> But only 189 bits dirty. This means the bits are just distributed
> across the disk (which is why you have 16/22 pages dirty).
>
> Any activity on the disk? 189 bits could easily be explained by a
> small amount of background disk activity on a disk that big.
That makes sense to me. I have:
$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid1]
md1 : active raid6 sde2[4] sdd2[3] sdc2[2] sdb2[1] sda2[0]
2929966080 blocks level 6, 512k chunk, algorithm 2 [5/5] [UUUUU]
bitmap: 2/4 pages [8KB], 131072KB chunk
Oh no! Half my array is dirty! But then:
# mdadm --examine-bitmap /dev/sdb2
Filename : /dev/sdb2
Magic : 6d746962
Version : 4
UUID : d8c57a89:166ee722:23adec48:1574b5fc
Events : 1338800
Events Cleared : 1338800
State : OK
Chunksize : 128 MB
Daemon : 5s flush period
Write Mode : Normal
Sync Size : 976655360 (931.41 GiB 1000.10 GB)
Bitmap : 7452 bits (chunks), 7 dirty (0.1%)
Not so bad after all.
On the other hand, repeatedly checking /proc/mdstat shows different
numbers of pages being dirty, and --examine-bitmap shows different
numbers of bits being dirty each time, whereas CoolCold managed 16 pages
repeatedly and 189 bits being dirty twice in a row. CoolCold, please can
you test --examine-bitmap again several times at least 5 seconds apart?
Cheers,
John.
next prev parent reply other threads:[~2011-08-31 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 9:58 possible bug - bitmap dirty pages status CoolCold
2011-08-31 9:05 ` CoolCold
2011-08-31 12:30 ` Paul Clements
2011-08-31 12:56 ` John Robinson [this message]
2011-08-31 13:16 ` CoolCold
2011-08-31 14:08 ` Paul Clements
2011-08-31 20:16 ` CoolCold
2011-09-01 5:40 ` NeilBrown
2011-11-14 23:11 ` linbloke
2011-11-16 2:30 ` NeilBrown
2011-11-21 21:50 ` linbloke
[not found] ` <CAGqmV7qpQBHLcJ9J9cP1zDw6kp6aLcaCMneFYEgcPOu7doXSMA@mail.gmail.com>
2011-11-16 3:07 ` NeilBrown
2011-11-16 9:36 ` CoolCold
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=4E5E2F7D.1010306@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=coolthecold@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=paul.clements@us.sios.com \
/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).