From: "kyle" <kylewong@southa.com>
To: "Andreas Dilger" <adilger@sun.com>, <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>
Subject: Re: need help with getting into a corrupted sub directory
Date: Mon, 1 Feb 2010 12:08:37 +0800 [thread overview]
Message-ID: <00c201caa2f4$3aa7dd00$b902a8c0@kyle> (raw)
In-Reply-To: 573A48EF-7CE3-481D-935E-364506424D1F@sun.com
>
> Well, I thought the same thing initially, but like the poster I have a
> drive which dies (locks up internally? I don't know) as soon as
> certain files are accessed. Since I could get 95%+ of the files
> using the "rsync -av --exclude-from {bad_file_list}" method, and the
> files I couldn't recover were of marginal value, I did that, as it was
> expedient.
>
90% of files I need is inside a subdirectly 'public' which cannot be read
........ :(
Kyle
next prev parent reply other threads:[~2010-02-01 4:15 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 [this message]
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='00c201caa2f4$3aa7dd00$b902a8c0@kyle' \
--to=kylewong@southa.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).