xfs
[Top] [All Lists]

Re: Lost+found

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: Lost+found
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 09 Apr 2008 08:11:13 -0500
Cc: Barry Naujok <bnaujok@xxxxxxx>, Jeffrey Sandel <webmaster@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <alpine.DEB.1.10.0804090628080.322@xxxxxxxxxxxxxxxx>
References: <1207632033.11530.10.camel@xxxxxxxxxxxxxxxxxxxxx> <op.t9bm23aa3jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.1.10.0804090628080.322@xxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
Justin Piszcz wrote:
> 
> On Wed, 9 Apr 2008, Barry Naujok wrote:
> 
>> On Tue, 08 Apr 2008 15:20:33 +1000, Jeffrey Sandel 
>> <webmaster@xxxxxxxxxxxxxx> 
>> wrote:
>>
>>> Recently I ran xfs_repair due to a firmware upgrade on an unmounted
>>> disk. The repair recovered the data but moved it to the lost+found
>>> directory.
>>>
>>> How do I recover file names and ownership?
>> The only real options you have AFAIK is the file command to try and identify
>> what type of file it is and just manually inspecting the files.
>>
>> Then, you might be able to derive its filename and where it came from.
>>
>> Regards,
>> Barry.
>>
> 
> Is there any chance this process could ever be improved so that the files 
> are restored back to their original locations or there is something that 
> keeps track of where they were located?

The whole reason they're in lost+found is because they are "orphaned" -
allocated & in use but not referenced by any directory... so the best
xfs_repair can do is rename to lost+found with the inode number.

Crosses my mind that one could probably write a generic tool which could
work with a package manager db to check file md5sums in /lost+found, if
the files happen to be system files installed via a package.... but if
they're files from your homedir or whatnot, it's tougher.

-Eric


<Prev in Thread] Current Thread [Next in Thread>