Well, Thank you for your help. I´m trying to restore files manually. I hope all were in /lost+found Talking about the problem. The server is a virtual host running. I use Xen to virtualize. Today I update the host that runs several virtual machines. After the update I reboot all the virtual machines. All of them start up right but this one appears with the problem of the fsck and then you know the history. Any suggestion about the real problem? can be the image file corrupted? Greetings, ESG 2010/11/17 <m.roth@xxxxxxxxx> > 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 > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
