xfs
[Top] [All Lists]

2.4.23-rc3+XFS internal error

To: linux-xfs@xxxxxxxxxxx
Subject: 2.4.23-rc3+XFS internal error
From: "Tomi Orava" <tomimo+linux-xfs@xxxxxxxxxxxxxxxxxx>
Date: Thu, 27 Nov 2003 10:14:22 +0200 (EET)
Importance: Normal
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: SquirrelMail/1.4.2
Hi,

I received the following error message last night, which obviously
resulted lots of problems while running xfs_repair, as the xfs_repair
was unable to get some inodes fixed properly, even though the repair
command was ran several times. In the end I found that the problematic
inodes belong to some directories which had been already moved to
lost+found directory and by renaming and the old lost+found
directory to other name and recreating the dir finally fixed those problems.
However, the xfs_repair still complains about "rebuilding directory inode
128" which belongs to "/" ... That one is still not fixed.

Unfortunately, the system is a production machine and I was unable
to properly investigate the error message, as it was important to get
the host back running ASAP.

The software configuration:

kernel-2.4.23-rc3+fullXFS (from bk)
The filesystem is on top of RAID1.
The xfsprogs I used in cleaning up the system were from
the RH9+XFS rescue-cd.

I have now booted the system back to 2.4.23-pre5+XFS
which has been working quite OK in the past weeks.
It would of course be nice to be able to get rid of
this still remaining xfs_repair error message, without
having to reformat the partition ...
I know that there is not much detailed information
in here, but perhaps I can be provide it later if
needed.

Regards,
Tomi Orava

Nov 27 00:10:30 alderan kernel: XFS internal error
XFS_WANT_CORRUPTED_RETURN at line 310 of file xfs_alloc.c.  Caller
0xc01d7da4
Nov 27 00:10:30 alderan kernel: c1c2f950 c01d6cbf c03a0841 00000001
00000000 c03a0835 00000136 c01d7da4
Nov 27 00:10:30 alderan kernel:        00000000 00000000 00000000 00000000
c1c2fb08 e6d50144 c1c2f9f8 c01d7da4
Nov 27 00:10:30 alderan kernel:        e6d50144 e6d500c0 000092a5 00000005
000092a5 00000002 00000002 000092a5
Nov 27 00:10:30 alderan kernel: Call Trace:
[xfs_alloc_fixup_trees+511/880]  [xfs_alloc_ag_vextent_near+2964/3232] 
[xfs_alloc_ag_vextent_near+2964/3232]  [xfs_alloc_ag_vextent+291/304] 
[xfs_alloc_vextent+747/912]  [xfs_bmap_alloc+2185/4880]  [scsi_done+0/160]
 [xfs_bmbt_get_state+47/64]  [xfs_bmapi+3714/5456] 
[xfs_bmbt_get_state+47/64]  [xfs_bmap_do_search_extents+184/976] 
[xfs_buf_item_unlock+162/208]  [xfs_trans_tail_ail+18/48] 
[xfs_bmap_search_extents+111/144]  [xfs_log_reserve+192/208] 
[xfs_iomap_write_allocate+679/1216]  [xfs_imap_to_bmap+57/528] 
[xfs_iunlock+61/128]  [xfs_iomap+1013/1328]  [map_blocks+94/208] 
[page_state_convert+1032/1280]  [ide_build_sglist+363/528] 
[ide_dma_intr+0/192]  [dma_timer_expiry+0/160] 
[linvfs_release_page+126/144]  [try_to_release_page+82/112] 
[shrink_cache+727/896]  [shrink_caches+61/96] 
[try_to_free_pages_zone+83/240]  [kswapd_balance_pgdat+94/160] 
[kswapd_balance+25/48]  [kswapd+146/176]  [kswapd+0/176]  [_stext+0/64] 
[arch_kernel_thread+46/64]  [kswapd+0/176]
Nov 27 00:10:30 alderan kernel: Call Trace: [<c01d6cbf>]  [<c01d7da4>] 
[<c01d7da4>]  [<c01d6ff3>]  [<c01d996b>]  [<c01e8679>]  [<c02b6490>] 
[<c01f36df>]  [<c01ece52>]  [<c01f36df>]  [<c01ea938>]  [<c01f5e72>] 
[<c0229c12>]  [<c01eacbf>]  [<c021a380>]  [<c023f9f7>]  [<c023e739>] 
[<c0211aed>]  [<c023ed05>]  [<c023a14e>]  [<c023af88>]  [<c02aec7b>] 
[<c02aea50>]  [<c02af120>]  [<c023b6be>]  [<c01416e2>]  [<c0136ce7>] 
[<c0136f1d>]  [<c0136f93>]  [<c013715e>]  [<c01371b9>]  [<c01372e2>] 
[<c0137250>]  [<c0105000>]  [<c01072ee>]  [<c0137250>]
Nov 27 00:10:30 alderan kernel: XFS internal error
XFS_WANT_CORRUPTED_RETURN at line 310 of file xfs_alloc.c.  Caller
0xc01d7da4
Nov 27 00:10:30 alderan kernel: c1c2f950 c01d6cbf c03a0841 00000001
00000000 c03a0835 00000136 c01d7da4
Nov 27 00:10:30 alderan kernel:        00000000 00000000 00000000 00000000
c1c2fb08 e6d500c0 c1c2f9f8 c01d7da4
Nov 27 00:10:30 alderan kernel:        e6d500c0 e6d50144 000092a5 00000005
000092a5 00000002 00000002 000092a5




<Prev in Thread] Current Thread [Next in Thread>