Hello,
we have encountered filesystem shutdown due:
Dec 29 11:09:11 localhost kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at
line 1610 of file xfs_alloc.c. Caller 0xc01d4354
Dec 29 11:09:11 localhost kernel: f64a7cb0 c01d3261 c03ec04a 00000001 00000000
c03ec03e 0000064a c01d4354
Dec 29 11:09:11 localhost kernel: 00000000 00000000 00000000 002379b1
00000008 00000001 002378ec 0000000f
Dec 29 11:09:11 localhost kernel: 00000001 00000000 00000000 f6e3b5b4
00000000 e90ba528 c01d4354 f6e3b5b4
Dec 29 11:09:11 localhost kernel: Call Trace: [xfs_free_ag_extent+1105/1904]
[xfs_free_extent+196/240] [xfs_free_extent+196/240] [xfs_trans_get_efd+56/80]
[xfs_bmap_finish+305/448]
Dec 29 11:09:11 localhost kernel: [xfs_itruncate_finish+527/1072]
[xfs_inactive+1280/1376] [vn_rele+175/192] [linvfs_clear_inode+24/48]
[clear_inode+176/192] [iput+199/688]
Dec 29 11:09:11 localhost kernel: [vfs_unlink+279/480] [nfsd_unlink+283/576]
[nfsd3_proc_remove+126/272] [nfs3svc_decode_diropargs+127/240]
[nfsd_dispatch+201/485] [nfsd_dispatch+0/485]
Dec 29 11:09:11 localhost kernel: [svc_process+887/1396] [nfsd+498/832]
[arch_kernel_thread+46/64] [nfsd+0/832]
Dec 29 11:09:11 localhost kernel: xfs_force_shutdown(device-mapper(254,3),0x8)
called from line 4073 of file xfs_bmap.c. Return address = 0xc023aaeb
Dec 29 11:09:11 localhost kernel: Filesystem "device-mapper(254,3)": Corruption
of in-memory data detected. Shutting down filesystem: device-mapper(254,3)
Dec 29 11:09:11 localhost kernel: Please umount the filesystem, and rectify the
problem(s)
[...reboot...]
Dec 29 11:24:38 localhost kernel: Linux version 2.4.28-smtp-2 (root@master)
(gcc version 3.3.4 (Debian 1:3.3.4-9ubuntu5)) #9 SMP Tue Dec 14 14:37:00 CET
2004
[...]
Dec 29 11:24:38 localhost kernel: XFS mounting filesystem device-mapper(254,3)
Dec 29 11:24:38 localhost kernel: Starting XFS recovery on filesystem:
device-mapper(254,3) (dev: device-mapper(254,3))
Dec 29 11:24:38 localhost kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at
line 1610 of file xfs_alloc.c. Caller 0xc01d4354
Dec 29 11:24:38 localhost kernel: f7509c10 c01d3261 c03ec04a 00000001 00000000
c03ec03e 0000064a c01d4354
Dec 29 11:24:38 localhost kernel: 00000000 00000000 00000000 002379b1
00000008 00000001 002378ec 0000000f
Dec 29 11:24:38 localhost kernel: 00000001 00000000 00000000 f69a7c50
f69a5e98 f6fbab8c c01d4354 f69a7c50
Dec 29 11:24:38 localhost kernel: Call Trace: [xfs_free_ag_extent+1105/1904]
[xfs_free_extent+196/240] [xfs_free_extent+196/240] [xfs_trans_get_efd+56/80]
[xlog_recover_process_efi+406/528]
Dec 29 11:24:38 localhost kernel: [xlog_recover_process_efis+118/144]
[xlog_recover_finish+32/196] [xfs_iunlock+62/128] [xfs_log_mount_finish+44/48]
[xfs_mountfs+2083/3792] [xfs_xlatesb+68/480]
Dec 29 11:24:38 localhost kernel: [xfs_mount+670/1200] [vfs_mount+67/80]
[linvfs_read_super+142/456] [alloc_super+26/432] [get_sb_bdev+411/640]
[alloc_vfsmnt+135/192]
Dec 29 11:24:38 localhost kernel: [do_kern_mount+285/304]
[do_add_mount+119/352] [do_mount+324/400] [copy_mount_options+101/192]
[sys_mount+190/288] [system_call+51/56]
Dec 29 11:24:38 localhost kernel: Ending XFS recovery on filesystem:
device-mapper(254,3) (dev: device-mapper(254,3))
This server is NFS mail backend (lots of small files, heavy IO, heavy load etc.)
I am scheduling xfs_check / xfs_recover to some after-midnight hours,
but meanwhile I would like to know if there is something I should
(shouldn't) do to repair and prevent this error.
O.
--
OndÅej Surà <ondrej@xxxxxxxx>
|