Ya it said if I couldnt mount it to use -L so I did. Apparently this was a
I dd_rescued all the data to a new drive, so drive isnt the issue anymore.
David Chinner wrote:
> On Thu, Dec 06, 2007 at 08:10:21AM -0800, Kingghost wrote:
>> So I was seeing my serial link go up and down so I rebooted and
>> was working fine, except my vg0 wouldnt mount. So I tried to xfs_repair
>> and this is the output I recieved.
>> slutb0x:/# xfs_repair -o assume_xfs /dev/vg0/media
>> Phase 1 - find and verify superblock...
>> sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with
>> calculated value 128
> NULLFSINO? Something has overwritten your superblock with a bunch of -1
>> resetting superblock root inode pointer to 128
>> sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent
>> calculated value 129
>> resetting superblock realtime bitmap ino pointer to 129
>> sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent
>> calculated value 130
>> resetting superblock realtime summary ino pointer to 130
>> Phase 2 - using internal log
>> - zero log...
> Uh-oh - you ran a xfs_repair -L, didn't you?
>> missing inbetween
>> rebuilding directory inode 1225702584
>> bad hash table for directory inode 1342177425 (no data entry): rebuilding
> And a bunch of trashed directory structures...
>> disconnected dir inode 752117670, moving to lost+found
>> disconnected inode 809433019, moving to lost+found
>> disconnected dir inode 823780059, moving to lost+found
>> disconnected dir inode 823780089, moving to lost+found
>> fatal error -- creation of .. entry failed (117), filesystem may be out
> 117 = EUCLEAN - corrupted filesystem. Sounds like there's more corruption
> there than was discovered or the underlying disk is still corruption
> What version of repair are you running ?
> This is a dying disk you're trying to repair right?
> Dave Chinner
> Principal Engineer
> SGI Australian Software Group
View this message in context:
Sent from the Xfs - General mailing list archive at Nabble.com.