From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Davidsen Subject: Re: 2.6.23.1: mdadm/raid5 hung/d-state Date: Thu, 08 Nov 2007 12:45:42 -0500 Message-ID: <47334B46.7000809@tmr.com> References: <18222.16003.92062.970530@notabene.brown> <47303FB8.7000801@systella.fr> <1194398700.2970.18.camel@dwillia2-linux.ch.intel.com> <47314653.80905@Lessem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <47314653.80905@Lessem.org> Sender: linux-raid-owner@vger.kernel.org To: Jeff Lessem Cc: Dan Williams , =?UTF-8?B?QkVSVFJBTkQgSm/Dq2w=?= , Justin Piszcz , Neil Brown , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org List-Id: linux-raid.ids 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. :-( > > I'm not sure if my problem is identical to these others, as mine only > seems to manifest with RAID5+XFS. The RAID rebuilds with no problem, > and I've not had any problems with RAID5+ext3. Hopefully it's not the raid which is the issue. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979