From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758399AbZBFUHl (ORCPT ); Fri, 6 Feb 2009 15:07:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753375AbZBFUHe (ORCPT ); Fri, 6 Feb 2009 15:07:34 -0500 Received: from mx2.redhat.com ([66.187.237.31]:44822 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753144AbZBFUHd (ORCPT ); Fri, 6 Feb 2009 15:07:33 -0500 Message-ID: <498C9876.3060208@redhat.com> Date: Fri, 06 Feb 2009 14:07:18 -0600 From: Eric Sandeen User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Alexander Beregalov CC: "linux-next@vger.kernel.org" , linux-ext4@vger.kernel.org, LKML Subject: Re: next-20090206: deadlock on ext4 References: <498C7671.1050309@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Alexander Beregalov wrote: > 2009/2/6 Eric Sandeen : >> Alexander Beregalov wrote: >>> Hi >>> >>> I run dbench on ext4 on loop device. >>> >>> EXT4-fs: barriers enabled >>> kjournald2 starting: pid 2420, dev loop0:8, commit interval 5 seconds >>> EXT4 FS on loop0, internal journal on loop0:8 >>> EXT4-fs: delayed allocation enabled >>> EXT4-fs: file extents enabled >>> EXT4-fs: mballoc enabled >>> EXT4-fs: mounted filesystem loop0 with ordered data mode >>> JBD: barrier-based sync failed on loop0:8 - disabling barriers >>> >>> INFO: task pdflush:2339 blocked for more than 120 seconds. >> Looks a lot like a bug I filed: >> >> http://bugzilla.kernel.org/show_bug.cgi?id=12579 >> >> but I'm having trouble reproducing it, now. I'll try dbench! > Yes, I can reproduce it easy with dbench. Do you only hit it on loopback? What is the filesystem hosting the loop file? Thanks, -Eric