#61 XFS internal error XFS_WANT_CORRUPTED_GOTO

Version_2.0
open
5
2014-08-20
2004-06-20
No

After performing heavy IO (reading all files from the
dm-34 device and writing them to another device), my
system freezed completely. After a hard reboot, I found
the following in kern.log:

---snip---
Jun 20 15:15:15 nikratio kernel: XFS internal error
XFS_WANT_CORRUPTED_GOTO at line 1583 of file
fs/xfs/xfs_alloc.c. Caller 0xe08e3602
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2525858/9781369]
xfs_free_ag_extent+0x451/0x770 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2530243/9781369]
xfs_free_extent+0xc2/0xf0 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2530243/9781369]
xfs_free_extent+0xc2/0xf0 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2745792/9781369]
xfs_ialloc_ag_alloc+0x4ff/0x660 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2884569/9781369]
xfs_trans_get_efd+0x38/0x50 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2607106/9781369]
xfs_bmap_finish+0x131/0x1c0 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2781072/9781369]
xfs_itruncate_finish+0x20f/0x430 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2907170/9781369]
xfs_inactive_free_eofblocks+0x291/0x2e0 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2909282/9781369]
xfs_inactive+0x101/0x560 [xfs]
Jun 20 15:15:15 nikratio kernel:
[cache_flusharray+80/256] cache_flusharray+0x50/0x100
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2977057/9781369] vn_rele+0xe0/0xf0 [xfs]
Jun 20 15:15:15 nikratio kernel:
[__crc_sleep_on+2970809/9781369]
linvfs_clear_inode+0x18/0x30 [xfs]
Jun 20 15:15:15 nikratio kernel: [clear_inode+166/192]
clear_inode+0xa6/0xc0
Jun 20 15:15:15 nikratio kernel: [dispose_list+77/176]
dispose_list+0x4d/0xb0
Jun 20 15:15:15 nikratio kernel:
[prune_icache+194/512] prune_icache+0xc2/0x200
Jun 20 15:15:15 nikratio kernel:
[shrink_icache_memory+40/48] shrink_icache_memory+0x28/0x30
Jun 20 15:15:15 nikratio kernel: [shrink_slab+331/384]
shrink_slab+0x14b/0x180
Jun 20 15:15:15 nikratio kernel:
[balance_pgdat+452/528] balance_pgdat+0x1c4/0x210
Jun 20 15:15:15 nikratio kernel: [kswapd+210/240]
kswapd+0xd2/0xf0
Jun 20 15:15:15 nikratio kernel:
[autoremove_wake_function+0/96]
autoremove_wake_function+0x0/0x60
Jun 20 15:15:15 nikratio kernel: [ret_from_fork+6/20]
ret_from_fork+0x6/0x14
Jun 20 15:15:15 nikratio kernel:
[autoremove_wake_function+0/96]
autoremove_wake_function+0x0/0x60
Jun 20 15:15:15 nikratio kernel: [kswapd+0/240]
kswapd+0x0/0xf0
Jun 20 15:15:15 nikratio kernel:
[kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Jun 20 15:15:15 nikratio kernel:
Jun 20 15:15:15 nikratio kernel:
xfs_force_shutdown(dm-34,0x8) called from line 4049 of
file fs/xfs/xfs_bmap.c. Return address = 0xe094fcdb
Jun 20 15:15:15 nikratio kernel: Filesystem "dm-34":
Corruption of in-memory data detected. Shutting down
filesystem: dm-34
Jun 20 15:15:15 nikratio kernel: Please umount the
filesystem, and rectify the problem(s)
Jun 20 15:17:17 nikratio kernel: Unable to handle
kernel NULL pointer dereference at virtual address 00000004
---snip---

The problem can be reproduced sometimes but not always.

Kernel is 2.6.7, evms 2.3.4, dm 2.6.7-rc2-udm1 patches.

dm-34 is a snapshot volume.

Please tell me what to do to help you searching the bug.

Discussion

  • Nikolaus Rath

    Nikolaus Rath - 2004-11-08

    Logged In: YES
    user_id=162840

    Hello,

    I just wanted to note that this bug still exists and is
    reproducable. Is there really nothing I can do to help you
    with fixing it? Activating a debug mode or something like this?

    I'd really like to see this fixed and I am willing to help
    actively, just tell me what to do.

    I've attached another error log.

     
  • Nikolaus Rath

    Nikolaus Rath - 2004-11-08

    Logged In: YES
    user_id=162840

    BTW, the system didn't freeze completely this time. I was
    able to continue my work.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks