On Mon, 2002-08-19 at 20:55, Thomas Hall wrote:
> I keep getting a recurrence of a defective directory inode with the
> same xfs_repair output every time. I get this from the latest
> xfs_repair snapshot as well as three other versions thereof:
>
> Matt R Hall
> mhall@xxxxxxxxxxxxxxx
>
Basically, you cannot leave files in lost+found when you run
repair. If you look at this output:
>
>
>
> Phase 2 - using internal log
> - zero log...
> - scan filesystem freespace and inode maps...
......
> - agno = 27
> - clearing existing "lost+found" inode
> - marking entry "lost+found" to be deleted
We just blew away lost+found - along with anything inside it.
Now we put them back again.
> - moving disconnected inodes to lost+found ...
> disconnected inode 100742368, moving to lost+found
> disconnected inode 100742370, moving to lost+found
> disconnected inode 100742387, moving to lost+found
> disconnected inode 100742390, moving to lost+found
> disconnected inode 100742407, moving to lost+found
> disconnected inode 100742420, moving to lost+found
> disconnected inode 100742422, moving to lost+found
> disconnected inode 100742429, moving to lost+found
> disconnected inode 100742432, moving to lost+found
> disconnected inode 100742464, moving to lost+found
> disconnected inode 100742482, moving to lost+found
> disconnected inode 100742484, moving to lost+found
> disconnected inode 100742486, moving to lost+found
> disconnected inode 100742490, moving to lost+found
> disconnected inode 100745856, moving to lost+found
> disconnected inode 100745903, moving to lost+found
> done
>
Try removing lost+found first, or just rename it to something
else. This will stop happening.
Steve
|