Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756327AbXFOBA4 (ORCPT ); Thu, 14 Jun 2007 21:00:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753675AbXFOBAq (ORCPT ); Thu, 14 Jun 2007 21:00:46 -0400 Received: from hancock.steeleye.com ([71.30.118.248]:54157 "EHLO hancock.sc.steeleye.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753003AbXFOBAp (ORCPT ); Thu, 14 Jun 2007 21:00:45 -0400 Message-ID: <4671E4BC.9080806@steeleye.com> Date: Thu, 14 Jun 2007 21:00:44 -0400 From: Paul Clements User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: Mike Snitzer CC: Neil Brown , linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, nbd-general@lists.sourceforge.net, Herbert Xu Subject: Re: raid1 with nbd member hangs MD on SLES10 and RHEL5 References: <170fa0d20706121930g3b89ddeex8b31c8923d2a0ff6@mail.gmail.com> <18031.22930.243723.550238@notabene.brown> <170fa0d20706121959w480213bcvaba1b6881710379f@mail.gmail.com> <170fa0d20706122009h5e3db54ek7487be4940a3d780@mail.gmail.com> <18031.25581.353761.802283@notabene.brown> <170fa0d20706122130q2c77d365tbe9261bab1a5b1b@mail.gmail.com> <170fa0d20706131123q17e4fb9ehe6be25a07462cc30@mail.gmail.com> <170fa0d20706131630p6cd29aa5i8f51856780a9c691@mail.gmail.com> In-Reply-To: <170fa0d20706131630p6cd29aa5i8f51856780a9c691@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 891 Lines: 22 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/