[TriLUG] /lost+found

[Jon Carnes]

The file fragments in /lost+found are from files that have lost or
corrupted inode information.  Fsck found them as files but without the
inode information it doesn't know what directory to associate them with,
so it associates them with /lost+found.  

It's very rare these days to find anything in /lost+found, unless you've
had a major crash.  Even then most of what you'll find in there are temp
files.  If your hard drive is slowly dieing then you will see files
becoming corrupt and you will also see files popping up in /lost+found
as inodes become corrupt.

In your situation I wouldn't worry too much.  Scan through the files and
then delete them.

HtH - Jon Carnes

On Wed, 2003-01-29 at 10:29, Joey O'Doherty wrote:
> I had an improper shutdown on my box yesterday and had to run fsck 
> manually to correct some problems (even though the filesystem was ext3). 
> Fortunately, everything seems fine except that I now have a number of 
> files in /lost+found.  Is there anything I do/anything I can learn from 
> these?  They all appear to be empty or give Input/output errors when I 
> try to read them.  Any howtos out there?  Google hasn't been very helpful.
> 
> thanks,
> /joeyo
> 
> -- 
> pub  1024D/B663781B 2001-11-13 Joey O'Doherty <joey(at)odoherty(dot)net>
> Key fingerprint = F76B 9ACA 4197 C707 6E4D  2B78 E430 101A B663 781B
> 
> _______________________________________________
> TriLUG mailing list
>     http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ:
>     http://www.trilug.org/~lovelace/faq/TriLUG-faq.html