From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Rudolf Zran <rudolfzran@yahoo.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"debian-user@lists.debian.org" <debian-user@lists.debian.org>
Subject: Re: Restoring filenames from partly damaged ext4-filesystem
Date: Fri, 10 Feb 2012 14:41:14 +0100 [thread overview]
Message-ID: <4F351E7A.2070005@fastmail.fm> (raw)
In-Reply-To: <1328822543.65833.YahooMailNeo@web132404.mail.ird.yahoo.com>
On 02/09/2012 10:22 PM, Rudolf Zran wrote:
> Hello Andreas!
>
>
> [ext4 partition overwritten with garbage at the beginning]
>
>
>>> * photorec from the testdisk package recoveres, luckily!, about 500GB of
>>> data. Though the content seems to be pretty reasonable, no filenames
>>> are recovered, since photorec operates without using filesystem
>>> knowledge.
>>>
>>> Do you see any chances (besides consulting professional recovery companies)
>>> getting the filenames back?
>>
>> There was an ext3grep tool that some people had success with, but when I
>> looked at it, it was still fairly complex to use.
>
> Thanks for the hint, but the problem with ext3grep is that it seems to
> rely on an intact filesystem structure. It even has no option to set
> another superblock besides the default one and fails with all commands
> I tried ( see https://pzt.me/8q6k ).
>
I have written some tools in the past to recover the file structure of
an over-formated ext3/ext4 device based on directory blocks.
With some tweaks it should be able to assign the file#inode_numbers in
lost+found to a directory structure.
Problem is that I'm rather busy with too many other projects already. Do
you know C and could you add some code on your own for the lost+found
assignment? I can assist you, but it is unlikely that I find much time
do it myself...
Cheers,
Bernd
next prev parent reply other threads:[~2012-02-10 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 16:29 Restoring filenames from partly damaged ext4-filesystem Rudolf Zran
2012-02-09 18:50 ` Andreas Dilger
2012-02-09 21:22 ` Rudolf Zran
2012-02-10 13:41 ` Bernd Schubert [this message]
2012-02-10 17:07 ` Rudolf Zran
2012-02-10 22:20 ` Bernd Schubert
2012-02-09 23:20 ` Walter Hurry
2012-02-10 18:02 ` Theodore Tso
2012-02-10 18:36 ` Rudolf Zran
2012-02-10 21:32 ` Ted Ts'o
2012-02-10 22:17 ` Bernd Schubert
2012-02-11 17:33 ` [SOLVED] (was "Re: Restoring filenames from partly damaged ext4-filesystem") Rudolf Zran
2012-02-11 18:30 ` Ted Ts'o
2012-02-11 18:47 ` Andreas Dilger
2012-02-11 18:50 ` Ted Ts'o
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=4F351E7A.2070005@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=adilger@dilger.ca \
--cc=debian-user@lists.debian.org \
--cc=linux-ext4@vger.kernel.org \
--cc=rudolfzran@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.