Re: xfs_repair: phase6.c:1129: mv_orphanage: Assertion `err == 2' failed.

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

 



On 9/15/19 7:44 AM, Arkadiusz Miśkiewicz wrote:
> 
> Hello.
> 
> xfsprogs 5.2.1 and:
> 
> disconnected dir inode 9185193405, moving to lost+found
> disconnected dir inode 9185193417, moving to lost+found
> disconnected dir inode 9185194001, moving to lost+found
> disconnected dir inode 9185194004, moving to lost+found
> disconnected dir inode 9185194010, moving to lost+found
> disconnected dir inode 9185194012, moving to lost+found
> disconnected dir inode 9185194018, moving to lost+found
> disconnected dir inode 9185194027, moving to lost+found
> disconnected dir inode 9185205370, moving to lost+found
> disconnected dir inode 9185209007, moving to lost+found
> corrupt dinode 9185209007, (btree extents).
> Metadata corruption detected at 0x449621, inode 0x2237b2aaf
> libxfs_iread_extents
> xfs_repair: phase6.c:1129: mv_orphanage: Assertion `err == 2' failed.
> Aborted

> 
> 
> # grep -A1 -B1 9185209007 log
> entry ".." at block 0 offset 80 in directory inode 9185141346 references
> non-existent inode 6454491396
> entry ".." at block 0 offset 80 in directory inode 9185209007 references
> free inode 62881485764
> entry ".." at block 0 offset 80 in directory inode 9185220220 references
> free inode 6454492606
> --
> rebuilding directory inode 9185141346
> entry ".." in directory inode 9185209007 points to free inode
> 62881485764, marking entry to be junked
> rebuilding directory inode 9185209007
> name create failed in ino 9185209007 (117), filesystem may be out of space

117 is EUCLEAN/EFSCORRUPTED even though we were in the process of rebuilding it. :(

so this is probably why a subsequent attempt to move it to lost+found failed as well?

Is this a metadumpable filesystem...?

-Eric

> entry ".." in directory inode 9185220220 points to free inode
> 6454492606, marking entry to be junked
> --
> disconnected dir inode 9185205370, moving to lost+found
> disconnected dir inode 9185209007, moving to lost+found
> corrupt dinode 9185209007, (btree extents).
> Metadata corruption detected at 0x449621, inode 0x2237b2aaf
> libxfs_iread_extents
> 



[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