From: Paul Clements <paul.clements@steeleye.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
nbd-general@lists.sourceforge.net,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
Date: Thu, 14 Jun 2007 21:00:44 -0400 [thread overview]
Message-ID: <4671E4BC.9080806@steeleye.com> (raw)
In-Reply-To: <170fa0d20706131630p6cd29aa5i8f51856780a9c691@mail.gmail.com>
Mike Snitzer wrote:
> Just a quick update; it is really starting to look like there is
> definitely an issue with the nbd kernel driver. I booted the SLES10
> 2.6.16.46-0.12-smp kernel with maxcpus=1 to test the theory that the
> nbd SMP fix that went into 2.6.16 was in some way causing this MD/NBD
> hang. But it _still_ occurs with the 4-step process I outlined above.
>
> The nbd0 device _should_ feel an NBD_DISCONNECT because the nbd-server
> is no longer running (the node it was running on was powered off)...
What do you mean, nbd should _feel_ an NBD_DISCONNECT ?
NBD_DISCONNECT is a manual process, not an automatic one.
--
Paul
prev parent reply other threads:[~2007-06-15 1:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 2:30 raid1 with nbd member hangs MD on SLES10 and RHEL5 Mike Snitzer
2007-06-13 2:42 ` Neil Brown
2007-06-13 2:59 ` Mike Snitzer
[not found] ` <170fa0d20706122009h5e3db54ek7487be4940a3d780@mail.gmail.com>
[not found] ` <18031.25581.353761.802283@notabene.brown>
[not found] ` <170fa0d20706122130q2c77d365tbe9261bab1a5b1b@mail.gmail.com>
2007-06-13 18:23 ` Mike Snitzer
2007-06-13 23:30 ` Mike Snitzer
2007-06-14 21:05 ` Bill Davidsen
2007-06-14 21:57 ` Mike Snitzer
2007-06-15 0:40 ` Paul Clements
2007-06-15 1:01 ` Mike Snitzer
2007-06-15 1:05 ` Paul Clements
2007-06-15 1:10 ` Mike Snitzer
2007-06-15 1:16 ` Paul Clements
2007-06-15 1:21 ` Mike Snitzer
2007-06-15 13:21 ` Bill Davidsen
2007-06-15 1:00 ` Paul Clements [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=4671E4BC.9080806@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=neilb@suse.de \
--cc=snitzer@gmail.com \
/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.