From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: libata for SATA HDs.
Date: Tue, 09 Aug 2005 23:27:51 +0100 [thread overview]
Message-ID: <42F92DE7.9070301@superbug.demon.co.uk> (raw)
In-Reply-To: <20050809180411.GD10315@havoc.gtf.org>
Jeff Garzik wrote:
> On Tue, Aug 09, 2005 at 06:55:23PM +0100, James Courtier-Dutton wrote:
>
>>Mark Lord wrote:
>>
>>>James Courtier-Dutton wrote:
>>>
>>>
>>>>Google did not help me.
>>>>
>>>>Can I use the kernel libata and do commands like this now? :
>>>>hdparm -S60 /dev/sda
>>>
>>>
>>>Yes, but only if you manually apply the "libata-passthru" patch.
>>>
>>>The copy (below) works with 2.6.12, and I'm including it here
>>>for the benefit of the many who aren't yet ready to adopt a new
>>>religion (git) just for obtaining this vital functionality.
>>>
>>>Cheers
>>>
>>
>>So, why hasn't that patch got into the kernel?
>
>
> Because there are several reports of it causing problems, when used on a
> loaded system.
>
> Jeff
>
Jeff,
What sort of problems? Loss of data?
I don't really have the time to do a full restore cycle just to try libata.
James
next prev parent reply other threads:[~2005-08-09 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42EEA9D5.5080304@superbug.demon.co.uk>
2005-08-09 13:40 ` libata for SATA HDs Mark Lord
2005-08-09 17:01 ` Erik Slagter
2005-08-09 17:55 ` James Courtier-Dutton
2005-08-09 18:04 ` Jeff Garzik
2005-08-09 22:27 ` James Courtier-Dutton [this message]
2005-08-10 2:28 ` Mark Lord
2005-08-09 18:18 ` Erik Slagter
2005-08-09 20:04 ` Mark Lord
2005-08-10 7:41 ` Erik Slagter
2005-08-10 18:42 Timothy Thelin
2005-08-11 3:21 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-08-12 1:04 Douglas Gilbert
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=42F92DE7.9070301@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--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).