🚀 go-pugleaf

On 2008-06-21, "Robert Swan" swan.r.l@gmail.com <"Robert Swan"> wrote:

> Can be a challenge finding where these things are documented, but
> "file" is often helpful when trying to work out what a file is.
>
> And it's not good to be finding things in lost+found.  That indicates
> some level of file system corruption

Alas - that was indeed the case.

I had a major crash. And my file system was corrupted very badly.
It is still unclear why it happened; but all is fixed now (apart
from the files in "lost+found") and I refrain from spelling out the
details.  However, I would have been history, if I had not had a backup
fully-operational (Linux) system on my box from which to repair the
corrupted disk partition.

Thank you for the advice and the pointer to the "file" command. The
output of the "file" command reads:

[felixk@ ~]$ file 75584621
75584621: ERROR: cannot open `75584621' (No such file or directory)

- which is probably just another indication that I was in big trouble!

I assume thaat I can safely delete the entries in "lost+found" since 
everything works again and none of the entries appear to be missed.

Felix







>
> -- perhaps due to yanking the

> power cord rather than shutting down cleanly.
>
> Have fun,
>
> Robert.


-- 
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)