public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Kervin Pierre <kpierre@fit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fs corruption recovery?
Date: Tue, 8 Jan 2002 20:07:05 -0700	[thread overview]
Message-ID: <20020108200705.S769@lynx.adilger.int> (raw)
In-Reply-To: <3C3BB082.8020204@fit.edu>
In-Reply-To: <3C3BB082.8020204@fit.edu>; from kpierre@fit.edu on Tue, Jan 08, 2002 at 09:52:50PM -0500

On Jan 08, 2002  21:52 -0500, Kervin Pierre wrote:
> I install and used 2.4.17 for about a week before my filesystem 
> corrupted.  I've tried 'fsck -a' but it complains that there was no 
> valid superblock found.

Try "e2fsck -B 4096 -b 32768 <device>" instead.

> Are there any tools or techniques that will recover data from the 
> corrupted filesystem even if there isn't a valid superblock?  Or is 
> there a way to write a temporary superblock so I can access the 
> information on the disk?

The ext2 format (includes ext3) has backup superblocks for just this reason.

> Lastly, if all else fails I'm going to try sending the drive one of 
> those 'file recovery companies'.  Does anyone have a recommendation for 
> a particular company?  I'm guessing that there'll be a few that wouldn't 
> know what to do with a ext3 partition.

Is the data really that valuable, and you don't have a backup?  It may
cost you several thousand dollars to do a recovery from such a company.
Yet, it isn't worth doing backups, it appears.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2002-01-09  3:07 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 [this message]
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
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=20020108200705.S769@lynx.adilger.int \
    --to=adilger@turbolabs.com \
    --cc=kpierre@fit.edu \
    --cc=linux-kernel@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