public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: raid1 + 2.6.27.7 issues
Date: Mon, 9 Feb 2009 14:56:21 -0600	[thread overview]
Message-ID: <cccedfc60902091256y5a280b0drb468c2757ffdb980@mail.gmail.com> (raw)
In-Reply-To: <4990843B.7010708@tmr.com>

On Mon, Feb 9, 2009 at 1:30 PM, Bill Davidsen <davidsen@tmr.com> wrote:
> Jon Nelson wrote:
>>
>> I don't think so. This is how I *remove* the nbd device:
>>
>> mdadm /dev/md11 --fail /dev/nbd0
>> sleep 3
>> mdadm /dev/md11 --remove /dev/nbd0
>>
>> and then finally nbd-client -d /dev/nbd0
>>
>> If necessary, I can try to simulate the problem by using a local
>> logical volume or some such.
>>
>
> I would try this with just the first step. I looked at the code briefly, and
> I think the write intent bitmap will not get built for a removed device but
> will for failed. In any case it's certainly something you can easily try.

Nope. :-(  --remove is necessary.

turnip:~ # mdadm --fail /dev/md11 /dev/nbd0
mdadm: set /dev/nbd0 faulty in /dev/md11
turnip:~ # mdadm --re-add /dev/md11 /dev/nbd0
mdadm: Cannot open /dev/nbd0: Device or resource busy
turnip:~ # mdadm --add /dev/md11 /dev/nbd0
mdadm: Cannot open /dev/nbd0: Device or resource busy
turnip:~ #


-- 
Jon

  parent reply	other threads:[~2009-02-09 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 16:36 raid1 + 2.6.27.7 issues Jon Nelson
2009-02-09 16:47 ` Iain Rauch
2009-02-09 16:59   ` Ray Van Dolson
2009-02-09 17:49     ` Jon Nelson
2009-02-09 17:53       ` Ray Van Dolson
2009-02-09 18:13         ` Jon Nelson
     [not found]       ` <4990843B.7010708@tmr.com>
2009-02-09 20:56         ` Jon Nelson [this message]
2009-02-09 17:25   ` Jon Nelson
2009-02-09 22:17 ` Neil Brown
2009-02-10  0:07   ` Jon Nelson
2009-02-11  5:06     ` 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=cccedfc60902091256y5a280b0drb468c2757ffdb980@mail.gmail.com \
    --to=jnelson-linux-raid@jamponi.net \
    --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