From: "NeilBrown" <neilb@suse.de>
To: Simon Jackson <sjackson@bluearc.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Write intent bitmaps.
Date: Tue, 25 Aug 2009 06:25:14 +1000 (EST) [thread overview]
Message-ID: <09198ab3b722ad5aa40d32f78626953e.squirrel@neil.brown.name> (raw)
In-Reply-To: <ABFC24E4C13D81489F7F624E14891C860D1F15EF@uk-ex-mbx1.terastack.bluearc .com>
On Tue, August 25, 2009 12:39 am, Simon Jackson wrote:
>
>
> I am trying to use write intent bitmaps on some RAID 1 volumes to reduce
> the rebuild times in the event of hard resets that cause the md driver to
> kick members out of my arrays.
>
> I used the mdadm --grow /dev/md0 --bitmap=internal and this appeared to
> succeed, but when I tried to examine the bitmap I get an error.
>
>
> :~$ sudo mdadm --grow /dev/md0 --bitmap=internal
> :~$ sudo mdadm -X /dev/md0
> Filename : /dev/md0
> Magic : 00000000
> mdadm: invalid bitmap magic 0x0, the bitmap file appears to be corrupted
> Version : 0
> mdadm: unknown bitmap version 0, either the bitmap file is corrupted or
> you need to upgrade your tools
Quoting from the man page:
-X, --examine-bitmap
Report information about a bitmap file. The argument is
either
an external bitmap file or an array component in case of
an
internal bitmap. Note that running this on an array
device
(e.g. /dev/md0) does not report the bitmap for that array.
Particularly read the last sentence.
Then try
mdadm -X /dev/sda5
NeilBrown
>
> cat /proc/mdstat
> Personalities : [raid1]
>
> md0 : active raid1 sda5[0] sdb5[1]
> 7823552 blocks [2/2] [UU]
> bitmap: 29/239 pages [116KB], 16KB chunk
>
> unused devices: <none>
> sjackson@mercuryst5:~$ sudo mdadm -X /dev/md0
> Filename : /dev/md0
> Magic : 00000000
> mdadm: invalid bitmap magic 0x0, the bitmap file appears to be corrupted
> Version : 0
> mdadm: unknown bitmap version 0, either the bitmap file is corrupted or
> you need to upgrade your tools
>
> Do I really have a usable bitmap on the device in this case?
>
> Thanks for any input.
>
>
> --
> 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-08-24 20:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 8:16 RAID 5 recovery to not degrade device on bad block Anshuman Aggarwal
2009-08-24 12:54 ` Goswin von Brederlow
2009-08-24 14:39 ` Write intent bitmaps Simon Jackson
[not found] ` <ABFC24E4C13D81489F7F624E14891C860D1F15EF@uk-ex-mbx1.terastack.bluearc .com>
2009-08-24 20:25 ` NeilBrown [this message]
2009-09-02 16:10 ` Bill Davidsen
2009-09-02 16:28 ` Paul Clements
2009-09-02 17:36 ` Ryan Wagoner
-- strict thread matches above, loose matches on Subject: below --
2009-06-08 2:10 Leslie Rhorer
2009-06-08 13:51 ` Carlos Carvalho
2009-06-18 8:17 ` Goswin von Brederlow
2009-06-19 2:24 ` Neil Brown
2009-06-19 5:21 ` Goswin von Brederlow
2009-06-19 2:16 ` Neil Brown
2009-06-19 15:01 ` Goswin von Brederlow
2009-06-20 8:14 ` NeilBrown
2009-06-20 9:52 ` Goswin von Brederlow
2009-06-21 18:06 ` Bill Davidsen
2009-06-28 18:14 ` Leslie Rhorer
2009-06-29 10:01 ` Goswin von Brederlow
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=09198ab3b722ad5aa40d32f78626953e.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=sjackson@bluearc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.