Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261160AbTHZPH7 (ORCPT ); Tue, 26 Aug 2003 11:07:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262983AbTHZPG2 (ORCPT ); Tue, 26 Aug 2003 11:06:28 -0400 Received: from mail3-126.ewetel.de ([212.6.122.126]:8137 "EHLO mail3.ewetel.de") by vger.kernel.org with ESMTP id S262951AbTHZPE7 (ORCPT ); Tue, 26 Aug 2003 11:04:59 -0400 Date: Tue, 26 Aug 2003 17:04:22 +0200 (CEST) From: Pascal Schmidt To: Marcelo Tosatti cc: linux-kernel@vger.kernel.org, , Subject: Re: [2.4.22-rc1] ext3/jbd assertion failure transaction.c:1164 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-CheckCompat: OK Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1442 Lines: 40 On Tue, 26 Aug 2003, Marcelo Tosatti wrote: > I've never seen this oops reported before. > Can you reproduce the problem? Yes. Running fsx directly on my ext3 /home partition gets me the BUG within a few seconds, with the exact same backtrace as below. There don't seem to be any jbd changes from -rc1 to final 2.4.22, so I assume the problem exists in 2.4.22 as well. Box survives a night of memtest86, so I figure it's not a memory problem. > > Assertion failure in journal_dirty_metadata() at transaction.c:1164: > > "jh->b_frozen_data == 0" > > kernel BUG at transaction.c:1164! > > >>EIP; c015dcc7 <===== > > Trace; c015581a > > Trace; c01637f7 <__jbd_kmalloc+27/a0> > > Trace; c015557d > > Trace; c0155906 > > Trace; c0155800 > > Trace; c01276cd > > Trace; c0127ad0 > > Trace; c01531ff > > Trace; c0132245 > > Trace; c0131e20 > > Trace; c0131fce > > Trace; c01088a3 -- Ciao, Pascal - 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/