On Fri, 1 Oct 1999, Trilochan Padhi wrote:
> While fixing a corrupted file system with fsck, I got a lot of
> messages about putting inodes in lost+found. Later, I saw a
> bunch of files with odd looking names in that directory.
>
> Q1) Is it OK to delete these files?
Yes. You might want to look at them first in case they are worth keeping,
though.
> Q2) What is the deal with these inodes?
>
fsck found some inodes which were marked as being in use, but were not
attached to any file in the filesystem. Each inode like this it finds, it
will link to a file /lost+found/#<inode number> so that you can restore
or destroy the file as you wish. Each inode will contain part or all of a
file whose directory entry got lost when the file system got corrupted.
There are two possible causes:
Either 1) the file was deleted from the directory structure, but the inode
remained (or equivalently, the inode was created, but the directory
structure never updated).
2) the inode doesn't actually contain anything, and its header and/or
the inode bmap got corrupted so it was marked as in use.
--
Mike <[EMAIL PROTECTED]>
Beware of low-flying butterflies.
