All of lore.kernel.org
 help / color / mirror / Atom feed
From: Spelic <spelic@shiftmail.org>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: mdadm incremental failed: md device busy
Date: Wed, 15 Dec 2010 18:50:11 +0100	[thread overview]
Message-ID: <4D08FFD3.9040406@shiftmail.org> (raw)

Hi there
this happened:

# cat /proc/mdstat
...other arrays not including sdb3...
md2 : active raid1 sda3[0]
       52428728 blocks super 1.2 [2/1] [U_]
       bitmap: 6/200 pages [24KB], 128KB chunk
...other arrays not including sdb3...

strangely sdb3 was not added to array at boot, I am still investigating 
that, but now see this:

# mdadm --incremental /dev/sdb3
mdadm: failed to open /dev/md2: Device or resource busy.


#strace mdadm --incremental /dev/sdb3
...lots of stuff, then...
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL)         = 0
open("/dev/md2", O_RDWR|O_EXCL)         = -1 EBUSY (Device or resource busy)
........
write(2, "mdadm: failed to open /dev/md2: "..., 57mdadm: failed to open 
/dev/md2: Device or resource busy.
) = 57


hmmm... strange thing, I just booted and md2 is not even mounted...
but now see this:

# mdadm /dev/md2 --add /dev/sdb3
mdadm: re-added /dev/sdb3

worked perfectly!

So?
Bug?

Thank you

             reply	other threads:[~2010-12-15 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 17:50 Spelic [this message]
2010-12-15 18:50 ` mdadm incremental failed: md device busy Spelic

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=4D08FFD3.9040406@shiftmail.org \
    --to=spelic@shiftmail.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.