http://oss.sgi.com/bugzilla/show_bug.cgi?id=296
------- Additional Comments From michele@xxxxxxxxxxx 2004-26-02 07:29 PDT
-------
Just wanted to chime in since I think I hit this bug (I'd tend to assume it is
related) as well. For me it happened with kernel 2.4.21 plus XFS. Machine is a
Samba 3 and Dhcp server. The volume is mounted via LVM.
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1623 of file xfs_alloc.c.
Caller 0xc018460b
f5709d68 c01ada2c 00000000 0001efe5 f5709dc8 c0183963 c02ec81c 00000001
00000000 c02ec7f6 00000657 c018460b 00000000 0001efe5 c866ee60 d481df34
e02bf000 00000000 e5639eec 0001eff0 0000000e 00000001 0001efe3 00000002
Call Trace: [<c01ada2c>] [<c0183963>] [<c018460b>] [<c018460b>] [<c0193873>]
[<c01b5aca>] [<c01cdbad>] [<c01de059>] [<c01dce84>] [<c014fb51>] [<c015046e>]
[<c014da66>] [<c0147b8d>] [<c01089d3>]
xfs_force_shutdown(lvm(58,0),0x8) called from line 4051 of file xfs_bmap.c.
Return address = 0xc01dd9da
Filesystem "lvm(58,0)": Corruption of in-memory data detected. Shutting down
filesystem: lvm(58,0)
Please umount the filesystem, and rectify the problem(s)
XFS mounting filesystem lvm(58,0)
Starting XFS recovery on filesystem: lvm(58,0) (dev: 58/0)
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1623 of file xfs_alloc.c.
Caller 0xc018460b
dfcbdc14 c01ada2c 00000000 0001efe5 dfcbdc74 c0183963 c02ec81c 00000001
00000000 c02ec7f6 00000657 c018460b 00000000 0001efe5 c866ee60 cc944594
e02bf000 00000000 e7d7ff70 0001eff0 0000000e 00000001 0001efe3 00000002
Call Trace: [<c01ada2c>] [<c0183963>] [<c018460b>] [<c018460b>] [<c01c0a82>]
[<c01c0af6>] [<c01c1e7c>] [<c01ba716>] [<c01c3924>] [<c01b8310>] [<c01ca4d1>]
[<c01dd78f>] [<c01dd552>] [<c013fbf2>] [<c0151b06>] [<c013fddd>] [<c0152be9>]
[<c0152ea2>] [<c0152d0d>] [<c01532cf>] [<c01089d3>]
Ending XFS recovery on filesystem: lvm(58,0) (dev: 58/0)
XFS mounting filesystem lvm(58,0)
Ending clean XFS mount for filesystem: lvm(58,0)
# xfs_info /opt/
meta-data=/opt isize=256 agcount=25, agsize=1048576 blks
= sectsz=512
data = bsize=4096 blocks=26214400, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=12800, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
# cat /proc/fs/xfs/stat
extent_alloc 7921 2030841 8064 2019641
abt 40568 257225 16302 16054
blk_map 18578027 148817 13666 148817 13695 18740562 1515917
bmbt 579 4325 61 18
dir 472061 8847 8712 325211
trans 5509 106952 5617
ig 462957 101776 188 361181 0 333701 21376
log 12220 251090 19 18906 6153
push_ail 118099 0 0 0 0 0 0 0 0 0
xstrat 4130 0
rw 2262088 17225932
attr 30753 9816 2 0
icluster 66981 27024 82509
vnodes 27480 362408 0 67931 334928 334928 334928 0
Running the first OOPS through ksymoops:
Trace; c01ada2c <xfs_error_report+58/5c>
Trace; c0183963 <xfs_free_ag_extent+55b/600>
Trace; c018460b <xfs_free_extent+b7/e0>
Trace; c018460b <xfs_free_extent+b7/e0>
Trace; c0193873 <xfs_bmap_finish+fb/180>
Trace; c01b5aca <xfs_itruncate_finish+1b6/2dc>
Trace; c01cdbad <xfs_inactive+211/428>
Trace; c01de059 <vn_rele+35/84>
Trace; c01dce84 <linvfs_clear_inode+10/1c>
Trace; c014fb51 <clear_inode+d5/114>
Trace; c015046e <iput+18a/298>
Trace; c014da66 <dput+f6/154>
Trace; c0147b8d <sys_rename+1d9/25c>
Trace; c01089d3 <system_call+33/38>
end here is the one during the repair:
Trace; c01ada2c <xfs_error_report+58/5c>
Trace; c0183963 <xfs_free_ag_extent+55b/600>
Trace; c018460b <xfs_free_extent+b7/e0>
Trace; c018460b <xfs_free_extent+b7/e0>
Trace; c01c0a82 <xlog_recover_process_efi+136/170>
Trace; c01c0af6 <xlog_recover_process_efis+3a/6c>
Trace; c01c1e7c <xlog_recover_finish+14/86>
Trace; c01ba716 <xfs_log_mount_finish+1e/2c>
Trace; c01c3924 <xfs_mountfs+ac8/bcc>
Trace; c01b8310 <xfs_ioinit+24/2c>
Trace; c01ca4d1 <xfs_mount+305/37c>
Trace; c01dd78f <vfs_mount+27/2c>
Trace; c01dd552 <linvfs_read_super+82/193>
Trace; c013fbf2 <get_sb_bdev+1de/258>
Trace; c0151b06 <alloc_vfsmnt+76/a0>
Trace; c013fddd <do_kern_mount+55/104>
Trace; c0152be9 <do_add_mount+69/138>
Trace; c0152ea2 <do_mount+146/160>
Trace; c0152d0d <copy_mount_options+55/a4>
Trace; c01532cf <sys_mount+af/110>
Trace; c01089d3 <system_call+33/38>
Hope this might give some more insight. let me know if I might provide further
info
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|