Skip to contentSkip to conversation

libata transport attributes

PATCH Dieter Stueken 2 participants 2 messages Apr 4, 2004 – Apr 5, 2004

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines · Jeff Garzik

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.

Signature · 4 lines
Dieter Stüken, con terra GmbH, Münster
    [email protected]
    http://www.conterra.de/
    (0)251-7474-501
#1 lore raw
Quoted 7 lines · Dieter Stueken
Quoted 2 lines · Jeff Garzik

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?

No. SMART would not be appropriate for a transport attribute either.

Quoted 4 lines

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?

Soon.

Jeff