http://bugme.osdl.org/show_bug.cgi?id=2277
------- Additional Comments From geek@xxxxxxxxxxxx 2004-04-03 15:05 -------
Same disaster happened again today.
The following error message appears in kernel log.
==========================================================================
Filesystem "lvm(58,5)": corrupt inode 167132010 ((a)extents = 623044872).
Unmount and run xfs_repair.
0x0: 49 4e 81 ed 01 02 00 01 00 00 03 ea 00 00 03 ea
Filesystem "lvm(58,5)": XFS internal error xfs_iformat_extents(1) at line 678
of file xfs_inode.c. Caller 0xc02004cb
d7f6dd20 c0200a31 c034e6c7 00000001 f715d800 c034e613 000002a6 c02004cb
c02004cb 03531db0 2522e908 c50af150 00000076 f0988a00 f715d800 8ac4c2b2
c02004cb c50af100 f0988a00 00000000 c50af22c c0200e2d c50af242 f0988a16
Call Trace: [<c0200a31>] [<c02004cb>] [<c02004cb>] [<c02004cb>] [<c0200e2d>]
[<c02016b2>] [<c01feb94>] [<c01ff127>] [<c021b69c>] [<c0220d20>] [<c022b7af>]
[<c014f1f2>] [<c014f990>] [<c014fcb9>] [<c0150019>] [<c014bf0f>] [<c010927f>]
==============================================================================
Unmount the partition and do xfs_repair on it, seems ok by far.
xfs_repair log is attactched below.
tux:~# xfs_repair -v /dev/vg0/data
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
zero_log: head block 187092 tail block 187092
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
bad non-zero extent size value 2301803360 for non-realtime inode 167132010,
resetting to zero
bad attr fork offset 118 in inode 167132010, should be 15
cleared inode 167132010
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
entry "recover_1.3b-1_powerpc.deb" at block 0 offset 440 in directory inode
167120659 references free inode 167132010
clearing inode number in entry at offset 440...
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- ensuring existence of lost+found directory
- traversing filesystem starting at / ...
rebuilding directory inode 167120659
- traversal finished ...
- traversing all unattached subtrees ...
- traversals finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|