Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757061AbZDFJVy (ORCPT ); Mon, 6 Apr 2009 05:21:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756056AbZDFJUs (ORCPT ); Mon, 6 Apr 2009 05:20:48 -0400 Received: from cantor.suse.de ([195.135.220.2]:33422 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755683AbZDFJUq (ORCPT ); Mon, 6 Apr 2009 05:20:46 -0400 Date: Mon, 6 Apr 2009 11:20:42 +0200 From: Jan Kara To: Alexander Beregalov Cc: Theodore Tso , "linux-next@vger.kernel.org" , linux-ext4@vger.kernel.org, LKML , sparclinux@vger.kernel.org Subject: Re: next-20090310: ext4 hangs Message-ID: <20090406092042.GA31189@duck.suse.cz> References: <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=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1872 Lines: 46 On Sun 05-04-09 01:09:31, Alexander Beregalov wrote: > 2009/4/2 Alexander Beregalov : > >>> > ?I'm helpless here. I don't see how we can miss a wakeup (plus you seem to > >>> > be the only one reporting the bug). Could you please compile and test 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 hit the > >>> > deadlock, please send me your kernel log. It should help with debugging why do > >>> > we miss the wakeup. Thanks. > >>> > >>> Which patch? > >> ?Ups. 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. > > I cannot reproduce it with vanilla v2.6.29. > It seems the problem has gone. > Thanks Jan. Thanks for testing. I'm glad we have one mystery less ;). > The patch output: > [133886.375874] JBD2: Waiting for ino 1062 > [133886.376372] JBD2: Waking up sleeper on ino 1062 > [133886.376824] JBD2: Woken on ino 1062 > [134611.108451] JBD2: Waiting for ino 1102 > [134611.108903] JBD2: Waking up sleeper on ino 1102 > [134611.109787] JBD2: Woken on ino 1102 > [134611.132912] JBD2: Waiting for ino 1074 > [134611.133311] JBD2: Waking up sleeper on ino 1074 > [134611.133707] JBD2: Woken on ino 1074 Yes, this is how it should always look... Honza -- Jan Kara SUSE Labs, CR -- 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/