Skip to contentSkip to conversation

Unexpected inode type 0160000 causes abort of xfs_repair

DISCUSSION Jonathan Groll 3 participants 4 messages Nov 22, 2006 – Dec 20, 2006 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

I'm unsuccesfully trying to repair an XFS filesystem

xfs_repair /dev/md1 and the same with -L both end with bad (negative) size -2150115811482766770 on inode 1539849750 cleared inode 1539849750
bad magic number 0x859b on inode 1539849751, resetting magic number bad version number 0xffffff88 on inode 1539849751, resetting version number
Unexpected inode type 0160000 inode 1539849751
Aborted

OS: debian sarge (stable)
Kernel: 2.6.15.7
xfsprogs 2.8.11-1

Is there anything I can possibly do?

Many thanks,
Jonathan Groll

#1 lore raw
Quoted 1 line · Jonathan Groll

Is there anything I can possibly do?

smash the inode using xfs_db (set mode to 0 should work) and run repair, it will prune it away for you

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 1 line · Barry Naujok

Can you try the attached patch and see how xfs_repair goes?

Many thanks, the patch worked like a charm! Is it going to be incorporated into the package in future?

Luckily I didn't have to blast the inode away, but I suspect that is exactly what the effect of the patch was ;-)

Thanks again,
Jonathan

#4 lore raw

Yes, this patch will be incorporated in the next xfsprogs update.

And yes, it did blast the inode away, as it wasn't really an inode (or very very corrupted if it was).

Quoted 17 lines

-----Original Message-----
From: Jonathan Groll [mailto:[email protected]]
Sent: Friday, 24 November 2006 12:14 AM
To: Barry Naujok; [email protected]
Subject: Re: Unexpected inode type 0160000 causes abort of xfs_repair

Quoted 1 line · Barry Naujok

Can you try the attached patch and see how xfs_repair goes?

Many thanks, the patch worked like a charm! Is it going to be incorporated into the package in future?

Luckily I didn't have to blast the inode away, but I suspect that is exactly what the effect of the patch was ;-)

Thanks again,
Jonathan