From: aristizb@ualberta.ca
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: SET_BITMAP_FILE assembling raid1
Date: Fri, 18 Sep 2009 11:35:44 -0600 [thread overview]
Message-ID: <20090918113544.11084l0ma4v10u0w@webmail.ualberta.ca> (raw)
In-Reply-To: <19123.11528.751595.835367@notabene.brown>
Hi Neil,
That is exactly the message I get in the kernel logs.
I tried ten times to assemble the array (waiting 2 seconds in between)
with no luck, but after 2-3 minutes it worked.
Quoting "Neil Brown" <neilb@suse.de>:
> On Thursday September 17, aristizb@ualberta.ca wrote:
>> Hi,
>>
>> After have stopped a raid1, I try to assemble it with one device and
>> its bitmap; but I received the following error message:
>>
>> $mdadm --assemble --force /dev/md2003 --bitmap=/tmp/md2003bm
>> /dev/syntropy21/ian_dvol_200_0_1
>>
>> mdadm: SET_BITMAP_FILE failed.
>>
>> After 5 minutes I retry the command and it succeeds, assembling the
>> raid without any problems.
>>
>>
>> It looks like mdadm cannot use the file I specified for the external
>> bitmap, but this file is not in use by any other raid. Is there any
>> explanation on why assemble could fail to create the raid with the
>> specified bitmap?
>
> If it failed once and then succeeded later it is most like that md
> thought the file was already in use in some way.
>
> If so there should be a message in the kernel logs saying something
> like:
> md2003: error: bitmap file is already in use
>
> Was there such a message?
>
> NeilBrown
>
>
>>
>>
>> Thank you.
>>
>>
>>
>> Juan.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2009-09-18 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 22:07 SET_BITMAP_FILE assembling raid1 aristizb
2009-09-18 6:47 ` Neil Brown
2009-09-18 17:35 ` aristizb [this message]
2009-09-25 7:37 ` 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=20090918113544.11084l0ma4v10u0w@webmail.ualberta.ca \
--to=aristizb@ualberta.ca \
--cc=linux-raid@vger.kernel.org \
--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