From: Neil Brown <neilb@suse.de>
To: "Lars Täuber" <taeuber@bbaw.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: equal size not large enough for RAID1?
Date: Fri, 7 Mar 2008 14:43:51 +1100 [thread overview]
Message-ID: <18384.47607.709703.403641@notabene.brown> (raw)
In-Reply-To: message from Lars Tauber on Thursday March 6
On Thursday March 6, taeuber@bbaw.de wrote:
>
> What is this internal bitmap good for? Is there a documentation
> somewhere on the net about this?
man md
and search for BITMAP. There is a section of BITMAP WRITE-INTENT
LOGGING.
>
> I just repeated the following:
>
> monosan:~ # mdadm -C /dev/md9 -l1 -n2 -x0 /dev/md4 /dev/etherd/e22.0
> mdadm: Defaulting to verion 1.0 metadata
> mdadm: /dev/md4 appears to be part of a raid array:
> level=raid1 devices=2 ctime=Thu Mar 6 09:39:37 2008
> mdadm: /dev/etherd/e22.0 appears to be part of a raid array:
> level=raid1 devices=2 ctime=Thu Mar 6 09:39:37 2008
> Continue creating array? y
> mdadm: array /dev/md9 started.
>
> monosan:~ # mdadm -V
> mdadm - v2.6.2 - 21st May 2007
>
> monosan:~ # mdadm /dev/md9 -f /dev/etherd/e22.0
> mdadm: set /dev/etherd/e22.0 faulty in /dev/md9
>
> monosan:~ # mdadm /dev/md9 -r /dev/etherd/e22.0
> mdadm: hot removed /dev/etherd/e22.0
>
> monosan:~ # mdadm /dev/md9 -a /dev/etherd/e22.0
> mdadm: /dev/etherd/e22.0 not large enough to join array
Hmm.. I just read through the change logs and I see there was a bug
here that was fixed in 2.6.3.
If you want an update from SuSE you would need to log a bug report in
the Novell bugzilla.
Alternately request v0.90 metadata (--metadata=0.90) That will avoid
the bug.
NeilBrown
next prev parent reply other threads:[~2008-03-07 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 9:05 equal size not large enough for RAID1? Lars Täuber
[not found] ` <18383.24086.165437.659336@notabene.brown>
2008-03-06 9:11 ` Lars Täuber
2008-03-07 3:43 ` Neil Brown [this message]
2008-03-07 11:08 ` Lars Täuber
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=18384.47607.709703.403641@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=taeuber@bbaw.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;
as well as URLs for NNTP newsgroup(s).