From: Tejun Heo <tj@kernel.org>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Artem Bokhan <aptem@ngs.ru>, Atila <atila.alr@dpf.gov.br>,
linux-ide@vger.kernel.org
Subject: Re: Faulty drive data recovery
Date: Fri, 26 Nov 2010 18:29:52 +0100 [thread overview]
Message-ID: <4CEFEE90.3030209@kernel.org> (raw)
In-Reply-To: <AANLkTikcPDOxcnb5tGMz9_mEgKntdwHHstO1CipMXv5+@mail.gmail.com>
Hello,
On 11/24/2010 06:00 PM, Greg Freemyer wrote:
>>>> HI, I'm trying to recover data from a damaged hard disk, which has
>>>> plenty of bad sectors, but also has many good ones. The problem is that
>>>> when a bad sector is found, the drive keeps trying to read it, instead
>>>> of giving up and just move on, so the average data read rate is around
>>>> 5Kb/s. With such rates, it will take more than an year to finish. Since
>>>> I'm using gnu ddrescue (which logs bad sectors, so one can try then
>>>> again later), my goal is not waste time with errors, leaving the retries
>>>> to a second round.
>>>> So, my first attempt was to drastically lower the timeouts in
>>>> libata-eh.c. It seems to have improved a little, but I'm not having more
>>>> than 12Kb/s.
>>>> Is there any way to minimize retries and make errors finish faster?
You can directly issue r/w commands using SGIO where you can control
retry and timeout explicitly. Hmm... it might be a good idea to allow
userland to set FAILFAST bit on a block device?
--
tejun
next prev parent reply other threads:[~2010-11-26 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 14:04 Faulty drive data recovery Atila
2010-11-24 16:03 ` Artem Bokhan
[not found] ` <AANLkTikhpPg4XMiDs8B7Jq=YC-xLYtemsarW5=EADkQM@mail.gmail.com>
2010-11-24 17:00 ` Greg Freemyer
2010-11-26 17:29 ` Tejun Heo [this message]
2010-11-26 18:45 ` Atila
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=4CEFEE90.3030209@kernel.org \
--to=tj@kernel.org \
--cc=aptem@ngs.ru \
--cc=atila.alr@dpf.gov.br \
--cc=greg.freemyer@gmail.com \
--cc=linux-ide@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).