From: Jeff Garzik <jgarzik@pobox.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] libata: add ioctls to support SMART
Date: Mon, 30 Aug 2004 13:44:11 -0400 [thread overview]
Message-ID: <4133676B.70800@pobox.com> (raw)
In-Reply-To: <41336570.8090308@wasp.net.au>
Brad Campbell wrote:
> John W. Linville wrote:
>
>> Support for HDIO_DRIVE_CMD and HDIO_DRIVE_TASK in libata. Useful for
>> supporting SMART w/ unmodified smartctl and smartd userland binaries.
>>
>> Not happy w/ loop after failed ata_qc_new_init(), but needed because
>> smartctl
>> and smartd did not retry after failure. Likely need an option to wait
>> for
>> available qc? Also not sure all the error return codes are correct...
>>
>
> YYYYYYYYYYEeeeeeeeeeeeeeeeeeeeeeeeeeehhhhhhhhhhaaaaaaaaaaaaaaaaaaa!!!!!!!!
>
> I know it's a bit kludgy and does not really fit the philosophy of
> libata but it works and it lets me keep an eye on my drives *now*.
>
> Although just for good measure I'll probably unmount and stop my raid
> arrays before I use it on the disks. Whats it like for locking on a busy
> system?
I wouldn't trust it on a busy system yet -- it submits the command to
the device without checking if there is a command already outstanding.
The patch could _definitely_ corrupt data or lock your hardware, since
it bypasses the SCSI mechanism that ensures that only one command is
executing at a time.
Jeff
next prev parent reply other threads:[~2004-08-30 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 15:31 [patch] libata: add ioctls to support SMART John W. Linville
2004-08-30 17:19 ` Jeff Garzik
2004-08-30 17:42 ` Andy Warner
2004-08-30 17:58 ` Jeff Garzik
2004-08-30 17:35 ` Brad Campbell
2004-08-30 17:44 ` Jeff Garzik [this message]
2004-08-30 17:47 ` Prakash K. Cheemplavam
2004-08-30 17:51 ` John W. Linville
2004-08-31 8:47 ` Prakash K. Cheemplavam
2004-08-31 8:47 ` Prakash K. Cheemplavam
2004-08-31 8:52 ` Jeff Garzik
2004-08-31 8:59 ` Prakash K. Cheemplavam
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=4133676B.70800@pobox.com \
--to=jgarzik@pobox.com \
--cc=brad@wasp.net.au \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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.