From: "Michael B. Trausch" <mbt@zest.trausch.us>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, mike-mobile@trausch.us
Subject: Re: ext4 undeletion question
Date: Tue, 28 Apr 2009 13:26:09 -0400 [thread overview]
Message-ID: <20090428132609.7628940e@zest.trausch.us> (raw)
In-Reply-To: <20090428161106.GB24043@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
On Tue, 28 Apr 2009 12:11:06 -0400
Theodore Tso <tytso@mit.edu> wrote:
> There is the program "ext3grep" which will look for older versions of
> the directory and inode table blocks in the journal. This can work,
> but unfortunately I don't think it's been extended to understand about
> the ext4 extent data structure.
Eh. Thanks for the mention... gave it a shot, but it seems to fail
nearly immediately:
Tuesday, 2009-Apr-28 at 13:21:41 - mbt@zest - Linux v2.6.29.1
Ubuntu Jaunty:[0-9/10014-0]:undel> sudo ext3grep --restore-all /dev/zestvg/home-retain-undelete
Running ext3grep version 0.10.1
WARNING: I don't know what EXT3_FEATURE_COMPAT_EXT_ATTR is.
ext3grep: ext3grep.cc:119: void run_program(): Assertion `be2le(journal_super_block.s_header.h_magic) == 0xc03b3998U' failed.
zsh: abort sudo ext3grep --restore-all /dev/zestvg/home-retain-undelete
I guess that means it won't work on an ext4 fs. :-)
I did create a snapshot of it using LVM (durr, I didn't think of that
before) so the FS is preserved as it was... I just don't know how to go
about digging through it to get the directory that I deleted out.
Hopefully I can figure that out before terribly long, as I am stuck
until I do...
--- Mike
--
Don't fix bugs later; fix them now.
--- Steve Maguire
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-28 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 14:42 ext4 undeletion question Michael B. Trausch
2009-04-28 16:11 ` Theodore Tso
2009-04-28 17:26 ` Michael B. Trausch [this message]
2009-04-28 17:55 ` Greg Freemyer
2009-04-28 18:53 ` Andreas Dilger
2009-04-28 19:29 ` Michael B. Trausch
2009-04-28 19:11 ` Michael B. Trausch
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=20090428132609.7628940e@zest.trausch.us \
--to=mbt@zest.trausch.us \
--cc=linux-ext4@vger.kernel.org \
--cc=mike-mobile@trausch.us \
--cc=tytso@mit.edu \
/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.