From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH 001 of 6] md: Fix an occasional deadlock in raid5 Date: Tue, 15 Jan 2008 23:15:04 -0800 Message-ID: <20080115231504.4df1b739.akpm@linux-foundation.org> References: <20080114123726.19968.patches@notabene> <1080114014525.20337@suse.de> <20080115215425.b1fcba31.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Dan Williams Cc: dean gaudet , NeilBrown , linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-raid.ids On Wed, 16 Jan 2008 00:09:31 -0700 "Dan Williams" wrote: > > heheh. > > > > it's really easy to reproduce the hang without the patch -- i could > > hang the box in under 20 min on 2.6.22+ w/XFS and raid5 on 7x750GB. > > i'll try with ext3... Dan's experiences suggest it won't happen with ext3 > > (or is even more rare), which would explain why this has is overall a > > rare problem. > > > > Hmmm... how rare? > > http://marc.info/?l=linux-kernel&m=119461747005776&w=2 > > There is nothing specific that prevents other filesystems from hitting > it, perhaps XFS is just better at submitting large i/o's. -stable > should get some kind of treatment. I'll take altered performance over > a hung system. We can always target 2.6.25-rc1 then 2.6.24.1 if Neil is still feeling wimpy.