From: Jan Kara <jack@suse.cz>
To: kyle <kylewong@southa.com>
Cc: Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
Subject: Re: need help with getting into a corrupted sub directory
Date: Tue, 9 Feb 2010 16:51:07 +0100 [thread overview]
Message-ID: <20100209155106.GD15318@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <00b601caa2f4$2564bf80$b902a8c0@kyle>
> >
> > 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.
>
> I need to get files from 'public/EL/', however, 'public' cause the drive die
> ........
>
> >
> >
> > debugfs is your friend. It can open and list a directory by inode
> > number, and dump the files to another filesystem.
>
> Is it possible to get the inode number of 'public/EL' without hitting the
> 'public' which cause the drive die?
Not easily. But as Ted pointed out, you might try to dd blocks from /dev/sde
upto the problematic block and then next time starting after the problematic block.
If this works out, you can then just run fsck at the resulting image and it should
recover the filesystem reasonably...
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
prev parent reply other threads:[~2010-02-09 15:51 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
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 [this message]
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=20100209155106.GD15318@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--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).