xfs
[Top] [All Lists]

Problem running xfs_repair - it crashes.

To: linux-xfs@xxxxxxxxxxx
Subject: Problem running xfs_repair - it crashes.
From: Paul Neilson <neilson.paul@xxxxxxxxx>
Date: Tue, 12 Apr 2005 22:22:45 +1000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=LEwNCuyWAUbpsF7dqsEVE96dRKl93LYJ16EF9iLVDfJkWNyIjBbE8cnCCRkLutQLxZzz1SFXdpM0MmsSuxPFImWj8gPEAvH9pHEVNyCkDW/t0nHKzXzPd2yaDAOx7tuYu/5Bmrz3Z1ZMm4dg5kChvJ69Mip0/CX/Ekj/g3HnfKE=
Reply-to: Paul Neilson <neilson.paul@xxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
I am trying to recover from a failed IDE controller.  I have installed
a new motherboard and all seems to be well except for some residual
disc problems.  I am running FC3   with xfsprogs-2.6.13-2 from
atrpms.net

When I run xfs_repair on my lvm logical volume (450GB over 3 discs), 
I get "xfs_repair: pwrite64 failed: Illegal seek"   as follows:


[root@moose src]# xfs_repair  /dev/VG0/myth
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
block (8,898667) already used, state 2
block (8,898668) already used, state 2
block (8,898669) already used, state 2
block (8,898670) already used, state 2
block (8,898671) already used, state 2
block (8,898672) already used, state 2
block (8,898673) already used, state 2
block (8,898674) already used, state 2
block (8,898675) already used, state 2
block (8,898676) already used, state 2
block (8,898677) already used, state 2
block (8,898678) already used, state 2
block (8,898679) already used, state 2
block (8,898680) already used, state 2
block (8,898681) already used, state 2
block (8,898682) already used, state 2
block (8,898683) already used, state 2
block (8,898684) already used, state 2
block (8,898685) already used, state 2
block (8,898686) already used, state 2
block (8,898687) already used, state 2
block (8,898688) already used, state 2
block (8,898689) already used, state 2
block (8,898690) already used, state 2
block (8,898691) already used, state 2
block (8,898692) already used, state 2
block (8,898693) already used, state 2
block (8,898694) already used, state 2
block (8,898695) already used, state 2
block (8,898696) already used, state 2
        - 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
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
corrupt block 0 in directory inode 544785218
        will junk block
no . entry for directory 544785218
no .. entry for directory 544785218
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - clear lost+found (if it exists) ...
        - clearing existing "lost+found" inode
        - deleting existing "lost+found" entry
xfs_repair: pwrite64 failed: Illegal seek
*** glibc detected *** free(): invalid pointer: 0x08696f70 ***
Aborted


There are clearly big problems with the disc as can be seen as follows:

[root@moose src]# xfs_repair -n  /dev/VG0/myth 
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
block (8,898667) already used, state 2
block (8,898668) already used, state 2
block (8,898669) already used, state 2
block (8,898670) already used, state 2
block (8,898671) already used, state 2
block (8,898672) already used, state 2
block (8,898673) already used, state 2
block (8,898674) already used, state 2
block (8,898675) already used, state 2
block (8,898676) already used, state 2
block (8,898677) already used, state 2
block (8,898678) already used, state 2
block (8,898679) already used, state 2
block (8,898680) already used, state 2
block (8,898681) already used, state 2
block (8,898682) already used, state 2
block (8,898683) already used, state 2
block (8,898684) already used, state 2
block (8,898685) already used, state 2
block (8,898686) already used, state 2
block (8,898687) already used, state 2
block (8,898688) already used, state 2
block (8,898689) already used, state 2
block (8,898690) already used, state 2
block (8,898691) already used, state 2
block (8,898692) already used, state 2
block (8,898693) already used, state 2
block (8,898694) already used, state 2
block (8,898695) already used, state 2
block (8,898696) already used, state 2
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
corrupt block 0 in directory inode 544785218
        would junk block
no . entry for directory 544785218
no .. entry for directory 544785218
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
corrupt block 0 in directory inode 544785218
        would junk block
no . entry for directory 544785218
no .. entry for directory 544785218
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem starting at / ... 
entry "video" in directory inode 128 not consistent with .. value
(18446744073709551615) in inode 544785218,
would junk entry "video"
        - traversal finished ... 
        - traversing all unattached subtrees ... 
corrupt block 0 in directory inode 544785218: would junk block
bad hash table for directory inode 544785218 (no data entry): would rebuild
would create missing "." entry in dir ino 544785218
        - traversals finished ... 
        - moving disconnected inodes to lost+found ... 
disconnected dir inode 544785218, would move to lost+found
disconnected inode 544785219, would move to lost+found
disconnected inode 544785220, would move to lost+found
disconnected inode 544785221, would move to lost+found
disconnected inode 544785222, would move to lost+found
disconnected inode 544785223, would move to lost+found
disconnected inode 544785224, would move to lost+found
disconnected inode 544785225, would move to lost+found
disconnected inode 544785226, would move to lost+found
disconnected inode 544785227, would move to lost+found
disconnected inode 544785228, would move to lost+found
disconnected inode 544785229, would move to lost+found
disconnected inode 544785230, would move to lost+found
disconnected inode 544785231, would move to lost+found
disconnected inode 544785232, would move to lost+found
disconnected inode 544785233, would move to lost+found
disconnected inode 544785234, would move to lost+found
disconnected inode 544785235, would move to lost+found
disconnected inode 544785236, would move to lost+found
disconnected inode 544785237, would move to lost+found
disconnected inode 544785238, would move to lost+found
disconnected inode 544785239, would move to lost+found
disconnected inode 544785240, would move to lost+found
disconnected inode 544785241, would move to lost+found
disconnected inode 544785242, would move to lost+found
disconnected inode 544785243, would move to lost+found
disconnected inode 544785244, would move to lost+found
disconnected inode 544785245, would move to lost+found
disconnected inode 544785246, would move to lost+found
disconnected inode 544785247, would move to lost+found
disconnected inode 545299776, would move to lost+found
disconnected inode 545299777, would move to lost+found
disconnected inode 545299778, would move to lost+found
disconnected inode 545299779, would move to lost+found
disconnected inode 545299780, would move to lost+found
disconnected inode 545299781, would move to lost+found
disconnected inode 545299782, would move to lost+found
disconnected inode 545299783, would move to lost+found
disconnected inode 545299784, would move to lost+found
disconnected inode 545299785, would move to lost+found
disconnected inode 545299786, would move to lost+found
disconnected inode 545299787, would move to lost+found
disconnected inode 545299788, would move to lost+found
disconnected inode 545299789, would move to lost+found
disconnected inode 545299790, would move to lost+found
disconnected inode 545299791, would move to lost+found
disconnected inode 545299792, would move to lost+found
disconnected inode 545299793, would move to lost+found
disconnected inode 545299794, would move to lost+found
disconnected inode 545299795, would move to lost+found
disconnected inode 545299796, would move to lost+found
disconnected inode 545299797, would move to lost+found
disconnected inode 545299798, would move to lost+found
disconnected inode 545299799, would move to lost+found
disconnected inode 545299800, would move to lost+found
disconnected inode 545299801, would move to lost+found
disconnected inode 545299802, would move to lost+found
disconnected inode 545299803, would move to lost+found
disconnected inode 545299804, would move to lost+found
disconnected inode 545299806, would move to lost+found
disconnected inode 545299807, would move to lost+found
disconnected inode 545299809, would move to lost+found
disconnected inode 545299816, would move to lost+found
disconnected inode 545299818, would move to lost+found
disconnected inode 545299826, would move to lost+found
disconnected inode 545299834, would move to lost+found
disconnected inode 545299839, would move to lost+found
disconnected inode 585614500, would move to lost+found
disconnected inode 585614501, would move to lost+found
disconnected inode 585614504, would move to lost+found
disconnected inode 585614507, would move to lost+found
disconnected inode 585614509, would move to lost+found
disconnected inode 585614511, would move to lost+found
disconnected inode 585614512, would move to lost+found
disconnected inode 585614513, would move to lost+found
disconnected inode 585614522, would move to lost+found
disconnected inode 585614523, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 128 nlinks from 9 to 8
No modify flag set, skipping filesystem flush and exiting.



Thanks in advance
Paul


<Prev in Thread] Current Thread [Next in Thread>
  • Problem running xfs_repair - it crashes., Paul Neilson <=