From: "Darius S. Naqvi" <dnaqvi@datagardens.com>
To: linux-raid@vger.kernel.org
Subject: Re: "mdadm --remove" fails if it is too soon after "mdadm --fail"
Date: Wed, 14 Oct 2009 12:38:24 -0600 (MDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0910141236260.14710@darius> (raw)
In-Reply-To: <alpine.DEB.1.00.0910131748110.8815@darius>
On Wed, 14 Oct 2009, Darius S. Naqvi wrote:
> I.e., it seems that the ioctl invoked by --fail doesn't directly set
> up the device to be ready for --remove, but some other kernel thread
> completes that state change. I'm wondering if it could be the case
> that when the system is very, very busy, it could take long enough for
> that kernel thread to run that it would cause what I see, i.e.,
> --remove fails with EBUSY, even though I've already waited about 20
> seconds for the device to be ready to be removed. If this is so, what
> shall I do? Here are the options I can think of:
Sorry to reply to my own posting. It turns out that in this case,
I've only waited 2.5 seconds. This may affect the probability of my
hunch being correct.
--
Darius S. Naqvi
dnaqvi@datagardens.com
http://www.datagardens.com
next prev parent reply other threads:[~2009-10-14 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 15:32 "mdadm --remove" fails if it is too soon after "mdadm --fail" Darius S. Naqvi
2009-10-14 18:38 ` Darius S. Naqvi [this message]
2009-10-15 1:49 ` NeilBrown
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=alpine.DEB.1.00.0910141236260.14710@darius \
--to=dnaqvi@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