public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: Eve Atley <eatley@wow-corp.com>
Cc: linux-newbie@vger.kernel.org
Subject: RE: Retrieving deleted files
Date: Wed, 07 Apr 2004 14:36:42 -0700	[thread overview]
Message-ID: <5.1.0.14.1.20040407141625.01f94748@celine> (raw)
In-Reply-To: <GNEPLLCIIBHICCOGIAKPEEGLCJAA.eatley@wow-corp.com>

At 05:06 PM 4/7/2004 -0400, Eve Atley wrote:

>Thanks so much for your help, Ray.
>
>I have tried the instructions at:
>http://recover.sourceforge.net/unix/
>(one of the first things I did try)
>...and I got a whole lot of garbage spit back to my screen; so much so, I
>had to quit.
>
>I am attempting to do something along these lines:
>
>         grep -a -B10000 -A0 "wowerpresumes" /dev/hdfb
>
>...and since I'm not sure what to put for B and A, I may be doing something
>wrong here. I don't recall how large the directory was 'before' things were
>deleted.

You do not need to know how large the directory was. This approach, as I 
read it (I've never actually used it myself), is limited to recovering text 
files. The trick is that you need to know something about the contents of 
some line of the file you want to recover. Then, you use grep to examine 
the raw partition (in this case, /dev/hdfb) as a single file (the -a switch 
tells grep to pretend the file is text), and it will turn up each instance 
of what you entered, reporting back  the  preceding "B" lines of text, the 
line itself, and "A" lines of following text.

Since you selected a very large value for B and 0 for A, you get a mess to 
the screen when you try this.

There is no general way to specify "right" values for A and B. You simply 
have to know something about the structure of the file. And since this 
approach will (I think) examine the filesystem linearly, a fragmented file 
will not be recoverable this way. Nor will a directory, which is really 
just a list of inode entries, which themselves can be scattered anywhere 
convenient on the filesystem. (And what I read about ext3 says the inode 
tables will be zero'd on deletion anyway.)

I did a bit more searching and still cannot find any undelete program 
tailored to ext3. I did find this one for ext2 -- 
http://www.data-recovery-software.net/Linux_Recovery.shtml -- that MIGHT be 
worth a look, since its description seems to indicate that it does not 
depend on the inode table to recover. And this one -- 
http://www.securiteam.com/tools/6R00T0K06S.html -- is not specific about 
what filesystems it will work on. The Debian package tct (Coroner's 
Toolkit) also includes a program called unrm, but I don't know if it is the 
same one.

Finally, my search turned up a couple of references to 
www.experts-exchange.com, a site that requires registration. You might want 
to check its resources.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-04-07 21:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 16:36 strange xcdroast bug solved Rei Shinozuka
2004-04-07 16:51 ` Retrieving deleted files Eve Atley
2004-04-07 17:37   ` Ray Olszewski
2004-04-07 18:25     ` Eve Atley
2004-04-07 18:54       ` Ray Olszewski
     [not found]         ` <GNEPLLCIIBHICCOGIAKPAEGKCJAA.eatley@wow-corp.com>
2004-04-07 20:42           ` Ray Olszewski
2004-04-07 21:06             ` Eve Atley
2004-04-07 21:36               ` Ray Olszewski [this message]
2004-04-11  6:29               ` Stephen Samuel
2004-04-08  5:38             ` pa3gcu

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=5.1.0.14.1.20040407141625.01f94748@celine \
    --to=ray@comarre.com \
    --cc=eatley@wow-corp.com \
    --cc=linux-newbie@vger.kernel.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