From: Neil Brown <neilb@suse.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Mike Snitzer <snitzer@gmail.com>, 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 12:41:41 +1000 [thread overview]
Message-ID: <18200.6501.186871.539817@notabene.brown> (raw)
In-Reply-To: message from Bill Davidsen on Thursday October 18
On Thursday October 18, davidsen@tmr.com wrote:
>
> Unless there's a substantial benefit from using the 1.0 format, you
> might want to go with something which works.
I am every grateful to the many people who do not just find work
arounds, but report problems and persist until they get fixed.
Obviously everyone should choose the path that suits them best, but
I'd rather we didn't discourage people who are working to get a bug
fixed.
> I would suggest using
> --bitmap-chunk, but the man page claims it doesn't apply to internal
> bitmaps. It also claims the bitmap size is chosen automatically to best
> use available space, but "doesn't work" seems an exception to "best
> use." ;-)
In this case, it does work, and it is best use. It just appears that
the 'available space' is not truly available - read error.
NeilBrown
next prev parent reply other threads:[~2007-10-19 2:41 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 [this message]
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
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.6501.186871.539817@notabene.brown \
--to=neilb@suse.de \
--cc=davidsen@tmr.com \
--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).