From: Neil Brown <neilb@suse.de>
To: Mike Snitzer <snitzer@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm 2.6.x regression, fails creation of raid1 w/ v1.0 sb and internal bitmap
Date: Fri, 19 Oct 2007 15:51:10 +1000 [thread overview]
Message-ID: <18200.17870.419986.530609@notabene.brown> (raw)
In-Reply-To: message from Mike Snitzer on Friday October 19
On Friday October 19, snitzer@gmail.com wrote:
>
> To further test this I used 2 local sparse 732456960K loopback devices
> and attempted to create the raid1 in the same manner. It failed in
> exactly the same way. This should cast further doubt on the bad block
> theory no?
Yes :-)
>
> I'm using a stock 2.6.19.7 that I then backported various MD fixes to
> from 2.6.20 -> 2.6.23... this kernel has worked great until I
> attempted v1.0 sb w/ bitmap=internal using mdadm 2.6.x.
>
> But would you like me to try a stock 2.6.22 or 2.6.23 kernel?
Yes please.
I'm suspecting the code in write_sb_page where it tests if the bitmap
overlaps the data or metadata. The only way I can see you getting the
exact error that you do get it for that to fail.
That test was introduced in 2.6.22. Did you backport that? Any
chance it got mucked up a bit?
I did the loopback test on current -mm and it works fine.
NeilBrown
next prev parent reply other threads:[~2007-10-19 5:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 15:37 mdadm 2.6.x regression, fails creation of raid1 w/ v1.0 sb and internal bitmap Mike Snitzer
2007-10-17 20:54 ` Bill Davidsen
2007-10-17 21:21 ` Mike Snitzer
2007-10-18 12:43 ` Bill Davidsen
2007-10-19 2:41 ` Neil Brown
2007-10-19 3:45 ` Bill Davidsen
2007-10-18 5:53 ` Neil Brown
2007-10-18 12:10 ` Mike Snitzer
2007-10-19 2:38 ` Neil Brown
2007-10-19 4:52 ` Mike Snitzer
2007-10-19 5:15 ` Mike Snitzer
2007-10-19 5:51 ` Neil Brown [this message]
2007-10-19 23:18 ` Mike Snitzer
2007-10-22 6:55 ` Neil Brown
2007-10-22 14:05 ` Mike Snitzer
2007-10-23 5:11 ` Neil Brown
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=18200.17870.419986.530609@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=snitzer@gmail.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).