From: Avantika Mathur <mathur@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: uninit block group/mballoc and fsstress
Date: Wed, 10 Oct 2007 17:37:08 -0700 [thread overview]
Message-ID: <470D7034.3090105@linux.vnet.ibm.com> (raw)
In-Reply-To: <470CFFE3.7080101@linux.vnet.ibm.com>
Aneesh Kumar K.V wrote:
> I am hitting this with the below config
>
> mke2fs -j -I 256 -O lazy_bg $dev
>
>
> mount -t ext4dev $dev /mnt/tmp -o "extents,mballoc"
>
> and running fsstress on /mnt/tmp/
I re-ran the test without the mballoc mount option, but with lazy_bg
enabled, and saw the same error. Error messages and stack are below.
mke2fs -j -I 256 -O lazy_bg $dev
mount -t ext4dev $dev /mnt/tmp -o "extents"
...
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc0000000001af07c
cpu 0x2: Vector: 300 (Data Access) at [c0000000fdf4b9b0]
pc: c0000000001af07c: .jbd2_journal_commit_transaction+0x11e8/0x1af4
lr: c0000000001af05c: .jbd2_journal_commit_transaction+0x11c8/0x1af4
sp: c0000000fdf4bc30
msr: 8000000000009032
dar: 0
dsisr: 40000000
current = 0xc0000000fc0f47f0
paca = 0xc000000000537880
pid = 5895, comm = kjournald2
enter ? for help
[c0000000fdf4be00] c0000000001b2994 .kjournald2+0xf4/0x2ac
[c0000000fdf4bf00] c00000000007afcc .kthread+0x84/0xd0
[c0000000fdf4bf90] c000000000027548 .kernel_thread+0x4c/0x68
2:mon>-- 0:conmux-control -- time-stamp -- Oct/10/07 11:28:02 --
-- 0:conmux-control -- time-stamp -- Oct/10/07 14:49:26 --
(bot:conmon-payload) disconnected
next prev parent reply other threads:[~2007-10-11 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 16:37 uninit block group/mballoc and fsstress Aneesh Kumar K.V
2007-10-11 0:37 ` Avantika Mathur [this message]
2007-10-11 4:46 ` Andreas Dilger
2007-10-11 6:56 ` Aneesh Kumar K.V
2007-10-11 7:45 ` Andreas Dilger
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=470D7034.3090105@linux.vnet.ibm.com \
--to=mathur@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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.