All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: Kervin Pierre <kpierre@fit.edu>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
	Andreas Dilger <adilger@turbolabs.com>,
	linux-kernel@vger.kernel.org
Subject: Re: fs corruption recovery?
Date: Thu, 10 Jan 2002 13:50:55 -0200	[thread overview]
Message-ID: <20020110135055.A1703@dea.linux-mips.net> (raw)
In-Reply-To: <3C3BB082.8020204@fit.edu> <20020108200705.S769@lynx.adilger.int> <200201090326.g093QBF27608@vindaloo.ras.ucalgary.ca> <3C3BC38C.7010808@fit.edu>
In-Reply-To: <3C3BC38C.7010808@fit.edu>; from kpierre@fit.edu on Tue, Jan 08, 2002 at 11:14:04PM -0500

On Tue, Jan 08, 2002 at 11:14:04PM -0500, Kervin Pierre wrote:

> Do you still have any of those scripts around? Or can you give me a 
> general idea of how you used debugfs to retrieve your files?

dd if=/dev/broken of=somefile conv=broken

> I was actually expecting to spend a few hundred instead of a few thousand.

Oh, the price tag for recovery of information from drive with heavier
physical damages are quite a bit juicier :-)

  Ralf

  parent reply	other threads:[~2002-01-11 23:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09  2:52 fs corruption recovery? Kervin Pierre
2002-01-09  3:07 ` Andreas Dilger
2002-01-09  3:26   ` Richard Gooch
2002-01-09  4:14     ` Kervin Pierre
2002-01-09  5:29       ` Richard Gooch
2002-01-09 11:10       ` Walter Hofmann
2002-01-10 15:50       ` Ralf Baechle [this message]
2002-01-09 10:24     ` Helge Hafting
2002-01-09 15:12       ` Richard Gooch
2002-01-09 15:22         ` Roy Sigurd Karlsbakk
2002-01-09 12:26     ` Bjorn Wesen
2002-01-09 20:29     ` Alex Bligh - linux-kernel
2002-01-09  4:03   ` Kervin Pierre
2002-01-09  5:20     ` H. Peter Anvin
2002-01-09  9:28   ` Thomas Capricelli
2002-01-09 10:43     ` Andreas Dilger

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=20020110135055.A1703@dea.linux-mips.net \
    --to=ralf@uni-koblenz.de \
    --cc=adilger@turbolabs.com \
    --cc=kpierre@fit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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.