From: Eric Sandeen Subject: Re: BUG_ON at mballoc.c:3752 Date: Fri, 08 Feb 2008 09:26:10 -0600 Message-ID: <47AC7492.1050907@redhat.com> References: <20080131140137.GA20780@alice> <20080131154207.GA22201@alice> <20080204060055.GC7494@skywalker> <1202335188.6886.15.camel@norville.austin.ibm.com> <20080207125548.GA8701@skywalker> <20080208150705.GA9111@alice> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "Aneesh Kumar K.V" , linux-ext4@vger.kernel.org, Dave Kleikamp To: Eric Sesterhenn Return-path: Received: from mx1.redhat.com ([66.187.233.31]:46048 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753651AbYBHP2R (ORCPT ); Fri, 8 Feb 2008 10:28:17 -0500 In-Reply-To: <20080208150705.GA9111@alice> Sender: linux-ext4-owner@vger.kernel.org List-ID: Eric Sesterhenn wrote: >> Eric , >> can you run the test with below patch and see if this makes any >> difference ?. I know we are not fixing any bugs in the below patch. > > ok, i checked out the old version again and applied both patches, > the BUG is gone (no surprise) > In the case where it would have hit the BUG i now get the following message: > > [ 740.400288] Aborting journal on device loop0. No message before that about *why* it aborted? > [ 740.405032] ext4_abort called. > [ 740.405097] EXT4-fs error (device loop0): ext4_journal_start_sb: Detected aborted journal > [ 740.405178] Remounting filesystem read-only > [ 740.410974] EXT4-fs error (device loop0) in ext4_ordered_write_end: IO failure > [ 740.414300] EXT4-fs error (device loop0) in ext4_reserve_inode_write: Journal has aborted > [ 740.414422] pa cba56990: logic 16, phys. 1953, len 16 > [ 740.414447] EXT4-fs error (device loop0): ext4_mb_release_inode_pa: free 4, pa_free 3 > [ 740.414548] EXT4-fs error (device loop0) in ext4_mb_free_blocks: Journal has aborted > > > Greetings, Eric