linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Juan Aristizabal <jaristizabal@datagardens.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm create problem with existing bitmap file
Date: Mon, 23 Aug 2010 12:15:27 +1000	[thread overview]
Message-ID: <20100823121527.61ca1ca4@notabene> (raw)
In-Reply-To: <4C6EB877.1050602@datagardens.com>

On Fri, 20 Aug 2010 11:16:39 -0600
Juan Aristizabal <jaristizabal@datagardens.com> wrote:

> Hello,
> 
> I am using mdadm 2.6.3 on Ubuntu 8.04.3 32 bits. Sometimes I hit this 
> error when I try to create a RAID1:
> 
> mdadm --create --force --assume-clean /dev/md73 --level=1 
> --bitmap=/root/bitmaps/md73bm.tmp --raid-devices=2 /dev/vg1/vol1 
> --write-mostly /dev/sdj
> 
> Continue creating array? mdadm: failed to open bitmap file 
> /root/bitmaps/md73bm.tmp: Text file busy
> 
> The bitmap file exists, but lsof doesn't show that it is in use by any 
> other process.
> 
> If I copy the bitmap file and try the create again everything works fine.
> 
> Any idea what might be happening here?

My best guess is that some other array is already using that bitmap file.  
   cat /proc/mdstat
should show you.
There aren't many circumstances that can create Text file busy - either the
file must be a binary that is being run, or a swap-file for which swapon has
been run, or the file is a bitmap file for an md array (maybe there are some
others, I cannot be bothered to grep just now).

NeilBrown


> 
> 
> Thanks,
> 
>  
> Juan Aristizabal
> 
> 
> --
> 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


      reply	other threads:[~2010-08-23  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 17:16 mdadm create problem with existing bitmap file Juan Aristizabal
2010-08-23  2:15 ` Neil Brown [this message]

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=20100823121527.61ca1ca4@notabene \
    --to=neilb@suse.de \
    --cc=jaristizabal@datagardens.com \
    --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).