On Thu, Jan 29, 2015 at 04:48:15PM +0100, SCHEFFER, Philippe wrote:
> I have a corrupted xfs filesytem. When I try to repair I get this error :
> disconnected inode 1427919, moving to lost+found
> corrupt dinode 1427919, extent total = 1, nblocks = 0. This is a bug.
> Please capture the filesystem metadata with xfs_metadump and
> report it to xfs@xxxxxxxxxxxx
> cache_node_purge: refcount was 1, not zero (node=0x1f6c19620)
> fatal error -- 117 - couldn't iget disconnected inode
> I captured metada with xfs_metadump but the file is 1,4Gb long. I can't send
> it to you.
> I printed inode1427919 :
> xfs_db> inode 1427919
> xfs_db> print
> core.magic = 0x494e
> core.format = 2 (extents)
> core.size = 2536
> core.nblocks = 1
> core.extsize = 0
> core.nextents = 1
> u.bmx = [startoff,startblock,blockcount,extentflag] 0:[0,320660992,1,0]
That's an inode with one extent of one block and looks perfectly
valid. We'll need the entire output of the xfs_repair run to see if
there were any prior actions taken on that inode by xfs_repair....