From: "NeilBrown" <neilb@suse.de>
To: aristizb@ualberta.ca
Cc: linux-raid@vger.kernel.org
Subject: Re: dirty chunks on bitmap not clearing (RAID1)
Date: Thu, 15 Oct 2009 12:36:22 +1100 [thread overview]
Message-ID: <70ff6a9cafb264616612d53002d9bd63.squirrel@neil.brown.name> (raw)
In-Reply-To: <20091014163943.15177bety75a30g0@webmail.ualberta.ca>
On Thu, October 15, 2009 9:39 am, aristizb@ualberta.ca wrote:
> Hello,
>
> I have a RAID1 with 2 LVM disks and I am running into a strange
> situation where having the 2 disks connected to the array the bitmap
> never clears the dirty chunks.
That shouldn't happen...
What versions of mdadm and the Linux kernel are you using?
NeilBrown
>
> I am assuming also that when a RAID1 is in write-through mode, the
> bitmap indicates that all the data has made it to all the disks if
> there are no dirty chunks using mdadm --examine-bitmap.
>
> The output of cat /proc/mdstat is:
>
> md2060 : active raid1 dm-5[1] dm-6[0]
> 2252736 blocks [2/2] [UU]
> bitmap: 1/275 pages [12KB], 4KB chunk, file: /tmp/md2060bm
>
>
> The output of mdadm --examine-bitmap /tmp/md2060bm is:
>
> Filename : md2060bm
> Magic : 6d746962
> Version : 4
> UUID : ad5fb74c:bb1c654a:087b2595:8a5d04a9
> Events : 12
> Events Cleared : 12
> State : OK
> Chunksize : 4 KB
> Daemon : 5s flush period
> Write Mode : Normal
> Sync Size : 2252736 (2.15 GiB 2.31 GB)
> Bitmap : 563184 bits (chunks), 3 dirty (0.0%)
>
>
> Having the array under no IO, I waited 30 minutes but the dirty data
> never gets clear from the bitmap, so I presume the disks are not in
> sync; but after I ran a block by block comparison of the two devices I
> found that they are equal.
>
> The superblocks and the external bitmap tell me that all the events
> are cleared, so I am confused on why the bitmap never goes to 0 dirty
> chunks.
>
> How can I tell if the disks are in sync?
>
>
> Thank you in advance for any help.
>
>
> --
> Juan Aristizabal
> --
> 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:[~2009-10-15 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 22:39 dirty chunks on bitmap not clearing (RAID1) aristizb
2009-10-15 1:36 ` NeilBrown [this message]
2009-10-15 15:15 ` aristizb
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 16:30 Chris Pearson
2011-08-31 7:38 ` NeilBrown
2011-08-31 18:23 ` Chris Pearson
2011-12-22 22:48 ` NeilBrown
2011-12-26 18:07 ` Alexander Lyakas
2012-01-02 22:58 ` 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=70ff6a9cafb264616612d53002d9bd63.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=aristizb@ualberta.ca \
--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).