From: "Marcel Partap" <mpartap@gmx.net>
To: "Marcel Partap" <mpartap@gmx.net>, tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, tytso@thunk.org
Subject: Re: Fwd: fsck ate my ext4 home partition, help!?
Date: Sun, 10 May 2009 17:25:20 +0200 [thread overview]
Message-ID: <20090510152520.262850@gmx.net> (raw)
In-Reply-To: <20090510145130.262830@gmx.net>
> I know some of the filenames that were in that directory. Is there any
> more usable method to find these inodes? for example, i know there was a
> symlink drive_c in there, and a file 'snippetz'. Can't i use this to somehow
> locate some of the dangling meta information? For sure it can't be all
> overwritten... If i grep the partition image for that filename and look up any
> resulting blocks with debugfs, is that getting me anywhere nearer the list of
> files in that directory?
Soo opening the image with hexedit and doing an ascii search for 'snippetz' right at the beginning gave me several locations which look an awful lot like lists of filenames in that directory. Converted the locations to decimal with echo $((16#hexnumber)) those are
0x28E450/0x438A2C0600 (Byte 2679888/290080949760)
0x1125450/0x438A2C0600 (Byte 17978448/290080949760)
0x114F450/0x438A2C0600 (Byte 18150480/290080949760)
0x1219450/0x438A2C0600 (Byte 18977872/290080949760)
Now what potential approaches could i take with debugfs now that it seems there are residual pieces of the directory? How to determine the corresponding inodes from the block number (position in bytes / 512, right?) - not clear to me from the man page...
regards marcel (slightly more optimistic now).
--
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-10 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 14:51 Fwd: fsck ate my ext4 home partition, help!? Marcel Partap
2009-05-10 15:25 ` Marcel Partap [this message]
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=20090510152520.262850@gmx.net \
--to=mpartap@gmx.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=tytso@thunk.org \
/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;
as well as URLs for NNTP newsgroup(s).