From: Roman Mamedov <roman@rm.pp.ru>
To: John Hendrikx <hjohn@xs4all.nl>
Cc: Neil Brown <neilb@suse.de>,
Miles Fidelman <mfidelman@meetinghouse.net>,
linux-raid@vger.kernel.org
Subject: Re: RAID6 and crashes (reporting back re. --bitmap)
Date: Fri, 11 Jun 2010 17:50:46 +0600 [thread overview]
Message-ID: <20100611175046.54b41aad@natsu> (raw)
In-Reply-To: <4C12199F.60108@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On Fri, 11 Jun 2010 13:10:23 +0200
John Hendrikx <hjohn@xs4all.nl> wrote:
> > I would be really interested to find out if my assumption of small numbers
> > of bits set is valid. You can find out the number of bits set at any
> > instant with "mdadm -X" run on some component of the array.
> >
> I was interested as well, so I ran this command:
>
> > mdadm -X /dev/md2
>
> and this is the result(??):
>
> Filename : /dev/md2
> Magic : d747992c
> mdadm: invalid bitmap magic 0xd747992c, the bitmap file appears to be
> corrupted
> Version : 1132474982
> mdadm: unknown bitmap version 1132474982, either the bitmap file is
> corrupted or you need to upgrade your tools
I stumbled in the same way initially, but then re-read more closely and
noticed that Neil said to run it "on some component of the array",
e.g. /dev/sdxN, not the array itself -- and that way it worked fine. However as
my array sees almost no write load at the moment, I have no useful results to
report.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-11 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 18:02 RAID6 and crashes Miles Fidelman
2010-06-10 18:57 ` Roman Mamedov
2010-06-10 21:22 ` RAID6 and crashes (reporting back re. --bitmap) Miles Fidelman
2010-06-10 21:41 ` Roman Mamedov
2010-06-10 22:40 ` Miles Fidelman
2010-06-11 2:51 ` Roman Mamedov
2010-06-11 4:31 ` Graham Mitchell
2010-06-11 4:41 ` Roman Mamedov
2010-06-11 12:13 ` Graham Mitchell
2010-06-11 4:42 ` Miles Fidelman
2010-06-11 4:50 ` Neil Brown
2010-06-13 14:28 ` Bernd Schubert
2010-06-13 23:05 ` Neil Brown
2010-06-14 9:01 ` Bernd Schubert
2010-06-14 9:14 ` Roman Mamedov
2010-06-14 9:47 ` Neil Brown
2010-06-14 11:53 ` Roman Mamedov
2010-06-14 21:24 ` Neil Brown
2010-06-11 4:46 ` Miles Fidelman
2010-06-11 4:55 ` Roman Mamedov
2010-06-11 20:26 ` Miles Fidelman
2010-06-11 5:08 ` Neil Brown
2010-06-11 11:10 ` John Hendrikx
2010-06-11 11:50 ` Roman Mamedov [this message]
2010-06-11 12:29 ` Graham Mitchell
2010-06-11 12:25 ` Graham Mitchell
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=20100611175046.54b41aad@natsu \
--to=roman@rm.pp.ru \
--cc=hjohn@xs4all.nl \
--cc=linux-raid@vger.kernel.org \
--cc=mfidelman@meetinghouse.net \
--cc=neilb@suse.de \
/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