From: Alexander Beregalov Subject: Re: next-20090310: ext4 hangs Date: Sun, 5 Apr 2009 01:09:31 +0400 Message-ID: References: <20090325151516.GB14881@atrey.karlin.mff.cuni.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: In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org 2009/4/2 Alexander Beregalov : >>> > =C2=A0I'm helpless here. I don't see how we can miss a wakeup (pl= us 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 t= o sleep >>> > waiting for inode commit and when we send wakeups etc. When you h= it the >>> > deadlock, please send me your kernel log. It should help with deb= ugging 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. I cannot reproduce it with vanilla v2.6.29. It seems the problem has gone. Thanks Jan. 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