From: Artem Bokhan <aptem@ngs.ru>
To: Atila <atila.alr@dpf.gov.br>
Cc: linux-ide@vger.kernel.org
Subject: Re: Faulty drive data recovery
Date: Wed, 24 Nov 2010 22:03:54 +0600 [thread overview]
Message-ID: <4CED376A.40502@ngs.ru> (raw)
In-Reply-To: <4CED1B5F.8000700@dpf.gov.br>
find /sys/devices -name timeout
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/timeout
/sys/devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/timeout
/sys/devices/pci0000:00/0000:00:1f.2/host3/target3:0:0/3:0:0:0/timeout
As I remember, some time ago somewhere in the sources was hardcoded 3 retries.
24.11.2010 20:04, Atila пишет:
> 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?
>
> Atila Romero
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-24 16:04 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 [this message]
[not found] ` <AANLkTikhpPg4XMiDs8B7Jq=YC-xLYtemsarW5=EADkQM@mail.gmail.com>
2010-11-24 17:00 ` Greg Freemyer
2010-11-26 17:29 ` Tejun Heo
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=4CED376A.40502@ngs.ru \
--to=aptem@ngs.ru \
--cc=atila.alr@dpf.gov.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.