Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761400AbXKHSCs (ORCPT ); Thu, 8 Nov 2007 13:02:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759866AbXKHSCi (ORCPT ); Thu, 8 Nov 2007 13:02:38 -0500 Received: from an-out-0708.google.com ([209.85.132.242]:4401 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759955AbXKHSCh (ORCPT ); Thu, 8 Nov 2007 13:02:37 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=IYmHbIdKcr6HCMbkIlMiZTZcjgal/zr3BC3WmhEbh5LLzTJHaM+71lhn1eAuCXqFU89eZVpnk3zeMksATRrV46SQP54Vk6YFMcrgE1Hgol2wQjdg1GBQ8I2VxzzdiYPZl92nZJ3v3vtMWMoqwebFxGSB2CHb5y23beRsDHfnNOU= Message-ID: Date: Thu, 8 Nov 2007 11:02:36 -0700 From: "Dan Williams" To: "Bill Davidsen" Subject: Re: 2.6.23.1: mdadm/raid5 hung/d-state Cc: "Jeff Lessem" , "=?ISO-8859-1?Q?BERTRAND_Jo=EBl?=" , "Justin Piszcz" , "Neil Brown" , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org In-Reply-To: <47334B46.7000809@tmr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <18222.16003.92062.970530@notabene.brown> <47303FB8.7000801@systella.fr> <1194398700.2970.18.camel@dwillia2-linux.ch.intel.com> <47314653.80905@Lessem.org> <47334B46.7000809@tmr.com> X-Google-Sender-Auth: 211c3939a6477d05 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1459 Lines: 32 On 11/8/07, Bill Davidsen wrote: > Jeff Lessem wrote: > > Dan Williams wrote: > > > The following patch, also attached, cleans up cases where the code > > looks > > > at sh->ops.pending when it should be looking at the consistent > > > stack-based snapshot of the operations flags. > > > > I tried this patch (against a stock 2.6.23), and it did not work for > > me. Not only did I/O to the effected RAID5 & XFS partition stop, but > > also I/O to all other disks. I was not able to capture any debugging > > information, but I should be able to do that tomorrow when I can hook > > a serial console to the machine. > > That can't be good! This is worrisome because Joel is giddy with joy > because it fixes his iSCSI problems. I was going to try it with nbd, but > perhaps I'll wait a week or so and see if others have more information. > Applying patches before a holiday weekend is a good way to avoid time > off. :-( We need to see more information on the failure that Jeff is seeing, and whether it goes away with the two known patches applied. He applied this most recent patch against stock 2.6.23 which means that the platform was still open to the first biofill flags issue. -- Dan - 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/