fsck errors and a lot of files in /lost+found

[m.roth at 5-cent.us]

Jonathan S Billings wrote:
> On 11/17/2010 07:37 AM, ESGLinux wrote:
>> Thanks, I can see some files testing first with file command.
>>
>> I´m looking for usefull files there but some I don´t know the right
>> place I have to copy (for example there is a lot of files that are
emails but I
>> don´t know the mailbox where I have to copy)
>>
>> is there any way to know the original location of the files?
>
> No, other from using the context you discover from 'file' or 'less'.
>
> That's why the directory is called lost+found -- fsck doesn't know where
> they're supposed to go.

And you're assuming, perhaps unconsciously, that you can reassemble the
files, which would be a *massive* amount of work in the case of an
executable.

Oh - what caused the problems in the first place? What type of filesystem
are you using? If it's a journaling one, like ext3 or 4, etc, then my
immediate concern would be whether the drive(s) needed to be replaced
->today<-

         mark