linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Andreas Dilger <adilger@sun.com>
Cc: kyle <kylewong@southa.com>, linux-ext4@vger.kernel.org
Subject: Re: need help with getting into a corrupted sub directory
Date: Sat, 30 Jan 2010 12:44:04 -0500	[thread overview]
Message-ID: <20100130174404.GC788@thunk.org> (raw)
In-Reply-To: <27FC5E2E-2F85-478A-95F2-1B9ED9D07690@sun.com>

On Sat, Jan 30, 2010 at 12:24:09AM -0700, Andreas Dilger wrote:
> On 2010-01-29, at 23:07, kyle wrote:
> >I have a ext3 filesystem created inside a problematic seagate
> >ST3500320AS
> >drive. The drive will just shut itself down automatically whenever
> >it hits
> >any read error. Only way to wake it up it to cold power off / on the
> >computer.
> 
> Strange, I had to do the same for a friend, and I think it was the
> same drive.
> You should put it into a USB enclosure - it speeds things up a lot.
> 
> >'sde' will disappeared from the system, need power off / on can
> >get it back.
> 
> To get most of the data off the dying drive, use rsync -v, and
> create a list
> of files to exclude, when you detect they cause the drive to die.

An image copy of the disk will tend to recover more than accessing the
disk via the file system.  I haven't run across the failure mode where
accessing a certain magic block causes the disk to die and require a
power cycle, but in that case what I'd probably do is enhance the
dd_rescue program to take a list of block numbers which it should skip
over....

This will require some programming, but it's probably the best way to
recover the most amount of data.  (Oh, and afterwards someone should
send the changes back to Kurt Garloff, since it would be a very useful
enhancement to dd_rescue.)

						- Ted

  reply	other threads:[~2010-01-30 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30  6:07 need help with getting into a corrupted sub directory kyle
2010-01-30  7:24 ` Andreas Dilger
2010-01-30 17:44   ` tytso [this message]
2010-01-31 18:11     ` Andreas Dilger
2010-02-01  4:08       ` kyle
2010-02-01  4:08   ` kyle
2010-02-09 15:51     ` Jan Kara

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=20100130174404.GC788@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=kylewong@southa.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).