Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN

Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN

[daniel+devel.linux.lkml]

[-- 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 --]

Re: Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN

[Alistair John Strachan]

On Friday 16 June 2006 15:09, daniel+devel.linux.lkml@flexserv.de wrote:
> 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?

Just make sure you've run memtest for at least a couple passes to eliminate 
bad RAM. This could still easily be an XFS bug, but it's worth checking.

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

Re: Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN

[daniel+devel.linux.lkml]

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:

> On Friday 16 June 2006 15:09, daniel+devel.linux.lkml@flexserv.de wrote:
>> What additional informatiuon can i get you?

On a tmpfs or ext2/3  i dont get it.

> Just make sure you've run memtest for at least a couple passes to eliminate 
> bad RAM. This could still easily be an XFS bug, but it's worth checking.
Its an full equiped E420R 4*450Mhz 4GB RAM.
I dont know  a memtesttool for sparcs.
If you know one please drop me a line.
every test from obp runs fine.

Daniel

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

Re: Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN

[Jan Engelhardt]

>Its an full equiped E420R 4*450Mhz 4GB RAM.
>I dont know  a memtesttool for sparcs.

Join the club, I am looking for one too.

Too bad that the Forth interpreter can only address a little less than 
640KB of memory (reminds me of DOS huh), otherwise I would have written a 
memchecker.

>If you know one please drop me a line.
>every test from obp runs fine.

There exists a userspace checker. It mlock()s a big chunk of memory and 
pokes on it like memtest86. It does not catch the few megabytes required 
for booting, but when you swap the upper half of the memory banks with the 
lower ones and rerun, you should get the same results of memtest86 would 
do.


Jan Engelhardt
-- 

Re: Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN

[Justin Piszcz]

How about:

SunVTS software



The SunVTS software executes multiple diagnostic hardware tests from a
single user interface, and is used to verify the configuration and
functionality of most hardware controllers and devices. The SunVTS 
software
operates primarily from a graphical user interface, enabling test 
parameters
to be set quickly and easily while a diagnostic test operation is being
performed.


http://docs.sun.com/source/817-7665/pmemtest.html

The pmemtest checks the physical memory of the system and reports hard and
soft error correction code (ECC) errors, memory read errors, and 
addressing problems. The pseudo driver mem is used to read the physical 
memory.


Note - 64-bit tests are located in the sparcv9 subdirectory:
/opt/SUNWvts/bin/sparcv9/testname, or the relative path to which you
installed SunVTS. If a test is not present in this directory, then it 
might
be available as a 32-bit test only. For more information, see 32-Bit and
64-Bit Tests



On Sat, 17 Jun 2006, Jan Engelhardt wrote:

>
>> Its an full equiped E420R 4*450Mhz 4GB RAM.
>> I dont know  a memtesttool for sparcs.
>
> Join the club, I am looking for one too.
>
> Too bad that the Forth interpreter can only address a little less than
> 640KB of memory (reminds me of DOS huh), otherwise I would have written a
> memchecker.
>
>> If you know one please drop me a line.
>> every test from obp runs fine.
>
> There exists a userspace checker. It mlock()s a big chunk of memory and
> pokes on it like memtest86. It does not catch the few megabytes required
> for booting, but when you swap the upper half of the memory banks with the
> lower ones and rerun, you should get the same results of memtest86 would
> do.
>
>
> Jan Engelhardt
> -- 
> -
> 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/
>

Re: Bug: XFS internal error XFS_WANT_CORRUPTED_RETURN

[Jan Engelhardt]

> How about:
>
> SunVTS software
>
Requires Solaris, which I presume those who run linux on it, have removed 
it :)

> The SunVTS software executes multiple diagnostic hardware tests from a
> single user interface, and is used to verify the configuration and
> functionality of most hardware controllers and devices. The SunVTS software
> operates primarily from a graphical user interface, enabling test parameters
                            ^^^^^^^^^
> to be set quickly and easily while a diagnostic test operation is being
> performed.
>
> http://docs.sun.com/source/817-7665/pmemtest.html
>
> The pmemtest checks the physical memory of the system and reports hard and
> soft error correction code (ECC) errors, memory read errors, and addressing
> problems. The pseudo driver mem is used to read the physical memory.
                                             ^^^^

Does not sound very promising :(


Jan Engelhardt
--