From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linux-ext4@vger.kernel.org,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Subject: Re: BUG_ON at mballoc.c:3752
Date: Fri, 08 Feb 2008 09:26:10 -0600 [thread overview]
Message-ID: <47AC7492.1050907@redhat.com> (raw)
In-Reply-To: <20080208150705.GA9111@alice>
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
next prev parent reply other threads:[~2008-02-08 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 14:01 BUG_ON at mballoc.c:3752 Eric Sesterhenn
2008-01-31 15:42 ` Eric Sesterhenn
2008-02-04 6:00 ` Aneesh Kumar K.V
2008-02-04 8:29 ` Eric Sesterhenn
2008-02-06 21:59 ` Dave Kleikamp
2008-02-07 12:55 ` Aneesh Kumar K.V
2008-02-08 1:30 ` Mingming Cao
2008-02-08 3:14 ` Aneesh Kumar K.V
2008-02-08 3:30 ` Eric Sandeen
2008-02-08 13:47 ` Eric Sesterhenn
2008-02-08 15:07 ` Eric Sesterhenn
2008-02-08 15:26 ` Eric Sandeen [this message]
2008-02-08 15:31 ` Eric Sesterhenn
2008-02-08 15:33 ` Eric Sandeen
2008-02-01 19:34 ` Mingming Cao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47AC7492.1050907@redhat.com \
--to=sandeen@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=snakebyte@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.