From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: RE: Retrieving deleted files
Date: Wed, 07 Apr 2004 11:54:12 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20040407114459.01efa728@celine> (raw)
In-Reply-To: <GNEPLLCIIBHICCOGIAKPCEGICJAA.eatley@wow-corp.com>
At 02:25 PM 4/7/2004 -0400, Eve Atley wrote:
>This question is actually a bit dependent on what filesystem the Linux host
>uses. For ext2, a couple of possibilities are (these are the Debian package
>names; your distro may differ a bit) "e2undel" and "recover".
>
> That answer is probably ext3fs - I'm running Linux Redhat 9,
> latest kernel.
>
> I did try recover, but could not get it to run; it says command
> not found.
>I have tried to install recover and gtkrecover.
When you "tried" to install recover (I assume from an rpm), did the install
procedure indicate that it had succeeded or not? If not, what did it say?
What is the "it" that says "command not found"? It is a message from the
shell (probably bash) that looks something like this:
ray@kuryakin:~$ recover
-bash: recover: command not found
Or does recover itself give you a message indicating that some other
command cannot be found? (I'm assuming you tried this from a command line,
not from the X frontend gtkrecover ... if not, please do so.)
Where is recover on the system?
Does "which recover" find it?
Does "find / -name recover" find it?
Were you trying to run recover as root or as an ordinary user? Could there
be a PATH issue (what happens if you specify the path to the app explicitly)?
I've no actual experience here, but I'd bet that recover will work on ext3
... in most respects, ext3 can fall back to ext2. And you can check
/etc/fstab for the relevant partition to see what filesystem type you are
using.
-
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
next prev parent reply other threads:[~2004-04-07 18:54 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 [this message]
[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
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.20040407114459.01efa728@celine \
--to=ray@comarre.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