From: daniel+devel.linux.lkml@flexserv.de
To: linux-kernel@vger.kernel.org
Subject: Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN
Date: Fri, 16 Jun 2006 16:09:11 +0200 [thread overview]
Message-ID: <878xnx19bs.fsf@xserver.flexserv.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 3437 bytes --]
Running 2.6.17-rc6
same when running it inside a new created partition.
No matter if on sda or inside a lvm on sdb
Reproducible.
Kernel is compiled with debug symbols i think.
What additional informatiuon can i get you?
Daniel
XFS internal error XFS_WANT_CORRUPTED_RETURN at line 298 of file
fs/xfs/xfs_alloc.c. Caller 0x0000000000586974
Call Trace:
[000000000058646c] xfs_alloc_ag_vextent+0x16c/0x1a0
[0000000000588b84] xfs_alloc_vextent+0x384/0x480
[0000000000595be0] xfs_bmap_btalloc+0x240/0x700
[0000000000598da8] xfs_bmapi+0xc08/0xec0
[00000000005be2ec] xfs_iomap_write_allocate+0x18c/0x3a0
[00000000005bd69c] xfs_iomap+0x27c/0x360
[00000000005da1ac] xfs_map_blocks+0x2c/0x80
[00000000005db33c] xfs_page_state_convert+0x3bc/0x640
[00000000005db638] xfs_vm_writepage+0x78/0x140
[00000000004c71e4] mpage_writepages+0x244/0x3c0
[000000000047ef40] do_writepages+0x60/0x80
[00000000004c5310] __sync_single_inode+0x50/0x240
[00000000004c5590] __writeback_single_inode+0x90/0x180
[00000000004c586c] sync_sb_inodes+0x1ec/0x320
[00000000004c5a80] writeback_inodes+0xe0/0x120
[000000000047ec34] wb_kupdate+0xb4/0x160
XFS internal error XFS_WANT_CORRUPTED_RETURN at line 298 of file
fs/xfs/xfs_alloc.c. Caller 0x0000000000586974
Call Trace:
[000000000058646c] xfs_alloc_ag_vextent+0x16c/0x1a0
[0000000000588b84] xfs_alloc_vextent+0x384/0x480
[0000000000595be0] xfs_bmap_btalloc+0x240/0x700
[0000000000598da8] xfs_bmapi+0xc08/0xec0
[00000000005be2ec] xfs_iomap_write_allocate+0x18c/0x3a0
[00000000005bd69c] xfs_iomap+0x27c/0x360
[00000000005da1ac] xfs_map_blocks+0x2c/0x80
[00000000005db33c] xfs_page_state_convert+0x3bc/0x640
[00000000005db638] xfs_vm_writepage+0x78/0x140
[00000000004c71e4] mpage_writepages+0x244/0x3c0
[000000000047ef40] do_writepages+0x60/0x80
[00000000004c5310] __sync_single_inode+0x50/0x240
[00000000004c5590] __writeback_single_inode+0x90/0x180
[00000000004c586c] sync_sb_inodes+0x1ec/0x320
[00000000004c5a80] writeback_inodes+0xe0/0x120
[000000000047ec34] wb_kupdate+0xb4/0x160
bilbao:~#
bilbao:~# XFS internal error XFS_WANT_CORRUPTED_RETURN at line 298 of
file fs/xfs/xfs_alloc.c. Caller 0x0000000000586974
Call Trace:
[000000000058646c] xfs_alloc_ag_vextent+0x16c/0x1a0
[0000000000588b84] xfs_alloc_vextent+0x384/0x480
[0000000000595be0] xfs_bmap_btalloc+0x240/0x700
[0000000000598da8] xfs_bmapi+0xc08/0xec0
[00000000005a518c] xfs_dir2_grow_inode+0x8c/0x2c0
[00000000005a69dc] xfs_dir2_sf_to_block+0x7c/0x520
[00000000005abfc0] xfs_dir2_sf_addname+0xe0/0x1a0
[00000000005a4a90] xfs_dir2_createname+0x130/0x160
[00000000005d6c3c] xfs_mkdir+0x3dc/0x660
[00000000005e1d60] xfs_vn_mknod+0x360/0x420
[00000000004aff90] vfs_mkdir+0x90/0x140
[00000000004b00f0] sys_mkdirat+0xb0/0x100
[0000000000406bd4] linux_sparc_syscall32+0x34/0x40
[0000000000010ba8] 0x10ba8
Filesystem "sda2": XFS internal error xfs_trans_cancel at line 1150 of
file fs/xfs/xfs_trans.c. Caller 0x00000000005d6abc
Call Trace:
[00000000005e1d60] xfs_vn_mknod+0x360/0x420
[00000000004aff90] vfs_mkdir+0x90/0x140
[00000000004b00f0] sys_mkdirat+0xb0/0x100
[0000000000406bd4] linux_sparc_syscall32+0x34/0x40
[0000000000010ba8] 0x10ba8
xfs_force_shutdown(sda2,0x8) called from line 1151 of file
fs/xfs/xfs_trans.c. Return address = 0x00000000005e57fc
Filesystem "sda2": Corruption of in-memory data detected. Shutting down
filesystem: sda2
Please umount the filesystem, and rectify the problem(s)
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2006-06-16 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 14:09 daniel+devel.linux.lkml [this message]
2006-06-16 17:35 ` Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN Alistair John Strachan
2006-06-16 21:38 ` daniel+devel.linux.lkml
2006-06-16 22:07 ` Jan Engelhardt
2006-06-16 22:11 ` Justin Piszcz
2006-06-17 9:25 ` Jan Engelhardt
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=878xnx19bs.fsf@xserver.flexserv.de \
--to=daniel+devel.linux.lkml@flexserv.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox