On Fri, Jul 07, 2017 at 01:50:09PM +0200, Emmanuel Florac wrote: > Le Fri, 7 Jul 2017 09:28:03 +1000 > Dave Chinner <david@xxxxxxxxxxxxx> écrivait: > > > > disconnected inode 26417468, moving to lost+found > > > disconnected inode 26417469, moving to lost+found > > > disconnected inode 26417470, moving to lost+found > > > > > > 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. > > Actually with xfs_repair 4.11 it's a different error in the end: > > disconnected inode 180399699751, moving to lost+found > disconnected inode 180399699752, moving to lost+found > > fatal error -- name create failed in lost+found (28), filesystem may be > out of space Would be helpful to have a metadump of this goobered-up lost+found fs... --D > > > -- > ------------------------------------------------------------------------ > Emmanuel Florac | Direction technique > | Intellique > | <eflorac@xxxxxxxxxxxxxx> > | +33 1 78 94 84 02 > ------------------------------------------------------------------------ -- 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
