Re: xfs_repair: couldn't map inode 2089979520, err = 117

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 18 Jan 2018, Brian Foster wrote:
> Christian, for the time being I suppose you could try a slightly older
> xfs_repair and see if that gets you anywhere. v4.10 or so appears to not
> include the associated commits.

OK, I've compiled v4.10.0 from source and gave it a try - and it 
succeeded: http://nerdbynature.de/bits/4.14/xfs/xfs_6.log 

This time it was able to complete phase 6 and 7 and moved 4.3 GB to 
lost+found (not bad for a 3.7 TB file system :)) 

I tried again with xfs_repair -n v4.12, but didn't dare running it w/o -n 
just yet: http://nerdbynature.de/bits/4.14/xfs/xfs_7.log

Thanks for your help here! If there are patches to try, let me know...

Christian.
-- 
BOFH excuse #66:

bit bucket overflow
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux