From: Alexander Beregalov Subject: Re: next-20090310: ext4 hangs Date: Thu, 2 Apr 2009 22:50:59 +0400 Message-ID: References: <20090325151516.GB14881@atrey.karlin.mff.cuni.cz> <20090325152234.GN23439@duck.suse.cz> <20090325161556.GP23439@duck.suse.cz> <20090325194316.GQ23439@duck.suse.cz> <20090331100150.GF11808@duck.suse.cz> <20090331123307.GG11808@duck.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Theodore Tso , "linux-next@vger.kernel.org" , linux-ext4@vger.kernel.org, LKML , sparclinux@vger.kernel.org To: Jan Kara Return-path: Received: from mail-ew0-f165.google.com ([209.85.219.165]:61980 "EHLO mail-ew0-f165.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753089AbZDBSvD convert rfc822-to-8bit (ORCPT ); Thu, 2 Apr 2009 14:51:03 -0400 In-Reply-To: <20090331123307.GG11808@duck.suse.cz> Sender: linux-ext4-owner@vger.kernel.org List-ID: >> > =C2=A0I'm helpless here. I don't see how we can miss a wakeup (plu= s you seem to >> > be the only one reporting the bug). Could you please compile and t= est the kernel >> > with the attached patch? It will print to kernel log when we go to= sleep >> > waiting for inode commit and when we send wakeups etc. When you hi= t the >> > deadlock, please send me your kernel log. It should help with debu= gging why do >> > we miss the wakeup. Thanks. >> >> Which patch? > =C2=A0Ups. Forgot to attach ;). Cannot reproduce it on current 2.6.29-git. Strange. It should already have all ext4/jbd2 patches from next-20090310, but anyway it happened with 2.6.29-rc8 also. I ran dbench in cycle on two indentical hosts for more than 24 hours with no hang tasks. I will try 2.6.29. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html