From: Dieter Stueken <stueken@conterra.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libata transport attributes
Date: Sun, 04 Apr 2004 17:06:58 +0200 [thread overview]
Message-ID: <40702492.8050603@conterra.de> (raw)
Jeff Garzik wrote:
> Since libata is leaving SCSI in 2.7, I would rather not add superfluous stuff like this at all.
> Further, you can already retrieve the information you export with _zero_ new code.
does this include informations about the drives SMART status, too?
The smartmotools (http://smartmontools.sourceforge.net/) won't work
with libata until some "passthrough" command gets implemented :-(
Will this be available soon (or even working now), or do I have to
wait until 2.7?
This is the main reason, that prevents me from switching to SATA now!
Just when writing these lines, I'm analyzing some prefail indications
from one of my 300G PATA disks via SMART. I have no problem, to replace
that disk now, but when running those disks blindly without SMART over
SATA, I certainly would loose those 300G very soon...
So, can you give us an idea of a time line about those things, please?
Dieter.
--
Dieter Stüken, con terra GmbH, Münster
stueken@conterra.de
http://www.conterra.de/
(0)251-7474-501
next reply other threads:[~2004-04-04 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 15:06 Dieter Stueken [this message]
2004-04-05 1:34 ` [PATCH] libata transport attributes Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-03-31 17:09 Justin Cormack
2004-03-31 21:07 ` Jeff Garzik
2004-04-01 11:56 ` Justin Cormack
2004-04-01 18:10 ` Jeff Garzik
2004-04-02 14:40 ` Justin Cormack
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=40702492.8050603@conterra.de \
--to=stueken@conterra.de \
--cc=linux-kernel@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