From: Neil Brown <neilb@suse.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Creating RAID1 with bitmap fails
Date: Thu, 31 May 2007 09:09:49 +1000 [thread overview]
Message-ID: <18014.1085.785167.411655@notabene.brown> (raw)
In-Reply-To: message from Jan Engelhardt on Wednesday May 30
On Wednesday May 30, jengelh@linux01.gwdg.de wrote:
>
> On May 30 2007 22:05, Neil Brown wrote:
> >>
> >> the following command strangely gives -EIO ...
> >> 12:27 sun:~ # mdadm -C /dev/md4 -l 1 -n 2 -e 1.0 -b internal /dev/ram0
> >> missing
> >>
> >> md: md4: raid array is not clean -- starting background reconstruction
> >> md4: failed to create bitmap (-5)
> >> md: pers->run() failed ...
> >> mdadm: RUN_ARRAY failed: Input/output error
> >> mdadm: stopped /dev/md4
> >>
> >> Leaving out -b internal creates the array. /dev/ram0 or /dev/sda5 - EIO
> >> happens on both. (But the disk is fine, like ram0)
> >> Where could I start looking?
> >>
> >> Linux sun 2.6.21-1.3149.al3.8smp #3 SMP Wed May 30 09:43:00 CEST 2007
> >> sparc64 sparc64 sparc64 GNU/Linux
> >> mdadm 2.5.4
> >
> >I'm fairly sure this is fixed in 2.6.2. It is certainly worth a try.
>
> The same command works on a x86_64 with mdadm 2.5.3...
Are you sure?
I suspect that the difference is more in the kernel version.
mdadm used to create some arrays with the bitmap positioned so that it
overlapped the data. Recent kernels check for that and reject the
array if there is an overlap. mdadm-2.6.2 makes sure not to create
any overlap.
NeilBrown
next prev parent reply other threads:[~2007-05-30 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 10:37 Creating RAID1 with bitmap fails Jan Engelhardt
2007-05-30 12:05 ` Neil Brown
2007-05-30 12:09 ` Jan Engelhardt
2007-05-30 23:09 ` Neil Brown [this message]
2007-05-31 4:07 ` Jan Engelhardt
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=18014.1085.785167.411655@notabene.brown \
--to=neilb@suse.de \
--cc=jengelh@linux01.gwdg.de \
--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).