From: Jeff Garzik <jeff@garzik.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Mark Lord" <lkml@rtr.ca>, "Rogério Brito" <rbrito@ime.usp.br>,
linux-kernel@vger.kernel.org
Subject: Re: Quick question about libata and hdparm
Date: Sun, 19 Apr 2009 08:57:23 -0400 [thread overview]
Message-ID: <49EB1FB3.5000609@garzik.org> (raw)
In-Reply-To: <49EB1C9C.3000105@msgid.tls.msk.ru>
Michael Tokarev wrote:
> Mark Lord wrote:
> []
>> Nearly all of the hdparm flags work fine with libata and SATA/PATA
>> drives.
>> Among the *very few* that do not, are the -m and -d flags. -c will be
>> working
>> in the newest kernels, but not yet in most distro kernels.
>>
>> The -d flag is not permitted by libata, as the kernel prefers to
>> completely
>> dictate DMA / PIO, and it does do a rather good job of it.
>
> Well, the kernel does a good job here in *almost* all cases.
> The problematic case is when a device has some bad/unreadable
> blocks/sectors. When such a place occurs on read, libata
> (or whatever it is) performs several retries, each time
> using "less aggressive" settings - like reducing UDMA and
> PIO mode till the lowest possible PIO/33. And the device
> stays in that mode until reboot, even if the problematic
> sector has been relocated. So it'd be nice to be able to
> reset the mode back in such cases.
Do you have a log?
libata worries about speed changes for CRC errors and the like, not for
media errors that involve sector relocation.
Jeff
next prev parent reply other threads:[~2009-04-19 12:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 0:22 Quick question about libata and hdparm Rogério Brito
2009-04-19 6:31 ` Robert Hancock
2009-04-19 12:33 ` Mark Lord
2009-04-19 12:44 ` Michael Tokarev
2009-04-19 12:57 ` Jeff Garzik [this message]
2009-04-19 13:06 ` Michael Tokarev
2009-04-19 20:11 ` Rogério Brito
2009-04-19 21:27 ` Jeff Garzik
2009-04-20 17:35 ` Rogério Brito
2009-04-20 18:40 ` Alan Cox
2009-04-20 20:41 ` Rogério Brito
2009-04-20 21:16 ` Alan Cox
2009-04-20 20:31 ` Bartlomiej Zolnierkiewicz
2009-04-20 20:45 ` Rogério Brito
2009-04-20 21:19 ` Alan Cox
2009-04-20 22:57 ` Rogério Brito
2009-04-21 5:32 ` Rogério Brito
2009-04-21 12:59 ` Bartlomiej Zolnierkiewicz
2009-04-23 5:56 ` Rogério Brito
2009-04-23 21:31 ` Bartlomiej Zolnierkiewicz
2009-04-24 3:00 ` Rogério Brito
2009-05-01 9:18 ` Rogério Brito
2009-05-01 10:31 ` Alan Cox
2009-05-01 11:50 ` Rogério Brito
2009-05-01 13:16 ` Alan Cox
2009-05-01 14:19 ` Rogério Brito
2009-05-01 11:20 ` Bartlomiej Zolnierkiewicz
2009-05-11 18:34 ` Jeff Garzik
2009-04-19 20:03 ` Rogério Brito
2009-04-19 23:41 ` Mark Lord
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=49EB1FB3.5000609@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mjt@tls.msk.ru \
--cc=rbrito@ime.usp.br \
/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.