From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kara Subject: Re: next-20090310: ext4 hangs Date: Mon, 6 Apr 2009 11:20:42 +0200 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-Transfer-Encoding: QUOTED-PRINTABLE Cc: Theodore Tso , "linux-next@vger.kernel.org" , linux-ext4@vger.kernel.org, LKML , sparclinux@vger.kernel.org To: Alexander Beregalov Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Sun 05-04-09 01:09:31, Alexander Beregalov wrote: > 2009/4/2 Alexander Beregalov : > >>> > =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 an= d 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 d= ebugging why do > >>> > we miss the wakeup. Thanks. > >>> > >>> Which patch? > >> =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 hour= s > > with no hang tasks. > > > > I will try 2.6.29. >=20 > 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 ;). =20 > 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 --=20 Jan Kara SUSE Labs, CR