Re: Weird xfs_repair error

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

 



Le Fri, 7 Jul 2017 09:28:03 +1000
Dave Chinner <david@xxxxxxxxxxxxx> écrivait:

> > 
> > fatal error -- name create failed in lost+found (117), filesystem
> > may be out of space  
> 
> Error 117. That's EFSCORRUPTED, not ENOSPC.  IOWs, lost+found was
> corrupted as it was being modified by xfs_repair.
> 
> > Even stranger, after mounting back the image, there is no lost+found
> > anywhere to be found! However the filesystem has lots of free space
> > and free inodes, how come?  
> 
> Because lost+found was corrupted.
> 
I've tried again with xfs_repair 4.11, not better. At the end, I've got
a "lost+found" directory, however, it I run xfs_repair again and again
it still ends with the same error... I'll try moving the old lost+found
out of the way.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@xxxxxxxxxxxxxx>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

Attachment: pgpzH6hVrsp9f.pgp
Description: Signature digitale OpenPGP


[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