From: Theodore Tso Subject: Re: next-20090310: ext4 hangs Date: Tue, 10 Mar 2009 11:47:45 -0400 Message-ID: <20090310154745.GF23075@mit.edu> References: <20090310124658.GE8840@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "linux-next@vger.kernel.org" , linux-ext4@vger.kernel.org, LKML To: Alexander Beregalov Return-path: Received: from THUNK.ORG ([69.25.196.29]:52872 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751777AbZCJPru (ORCPT ); Tue, 10 Mar 2009 11:47:50 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On Tue, Mar 10, 2009 at 05:18:55PM +0300, Alexander Beregalov wrote: > > Thanks for reporting this; does it show up on stock 2.6.29-rc7? > No, I can not reproduce it. > It is a slow system, I would not like to bisect it, only if it is the > last possibility. Just to be clear; you weren't able to reproduce it on stock 2.6.29-rc7 ---- does it reproduce easily on linux-next? Next question --- does the system hang completely, or just the dbench process (and probably any process that tries touching the filesystem that's hung up)? Do you have a serial console, or someone of recording all of the dumps coming from sysrq-t? The two stack traces you gave weren't the ones causing the problem, but rather the ones waiting for the journal lock. I don't think is related to BZ #12579, although some of the symptoms look superficially the same. - Ted P.S. What are your dbench parameters, and how big is your filesystem, so I can try to reproduce it on my side? And how long do you typically need to run before this triggers? Thanks!