From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Barry Naujok <bnaujok@sgi.com>,
Jeffrey Sandel <webmaster@javainbaja.com>,
xfs@oss.sgi.com
Subject: Re: Lost+found
Date: Wed, 09 Apr 2008 08:11:13 -0500 [thread overview]
Message-ID: <47FCC071.40201@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0804090628080.322@p34.internal.lan>
Justin Piszcz wrote:
>
> On Wed, 9 Apr 2008, Barry Naujok wrote:
>
>> On Tue, 08 Apr 2008 15:20:33 +1000, Jeffrey Sandel <webmaster@javainbaja.com>
>> 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
next prev parent reply other threads:[~2008-04-09 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 5:20 Lost+found Jeffrey Sandel
2008-04-09 2:12 ` Lost+found Barry Naujok
2008-04-09 10:28 ` Lost+found Justin Piszcz
2008-04-09 13:11 ` Eric Sandeen [this message]
2008-04-09 13:29 ` Lost+found Christoph Hellwig
2008-04-11 2:07 ` Lost+found Niv Sardi
2008-04-10 8:51 ` Lost+found Emmanuel Florac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47FCC071.40201@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@sgi.com \
--cc=jpiszcz@lucidpixels.com \
--cc=webmaster@javainbaja.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox