From: Tejun Heo <htejun@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Soeren Sonnenburg <kernel@nn7.de>, Jeff Garzik <jeff@garzik.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: SATA hotplug from the user side ?
Date: Tue, 23 Jan 2007 15:23:03 +0900 [thread overview]
Message-ID: <45B5A9C7.5050700@gmail.com> (raw)
In-Reply-To: <20070122210312.GD4516@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
> Does SATA electrical conector keying let the disk firmware unload
> heads before the user manages to pull it out enough to sever power?
I don't think so.
> If it does not, the drive will do an emergency head unload, which is
> not good and will likely reduce the drive's lifetime.
Probably.
> Using hdparm -Y before the unplug, or scsiadd -r (on a kernel that
> has Tejun's new patch to optionally issue an START_STOP_UNIT to the
> SCSI device enabled) is probably a good idea. Unless it is a shared
> SATA port (I don't know if such a thing exists yet) and another box
> is talking to the disk, etc.
Agreed. But it would be *much* better if all these can be taken care of
by hald and its minions. Such that the user can just tell the system
that the hdd is going to be removed and all these dirty tricks are done
automagically.
--
tejun
next prev parent reply other threads:[~2007-01-23 6:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 7:57 SATA hotplug from the user side ? Soeren Sonnenburg
2007-01-12 17:04 ` Jeff Garzik
2007-01-12 22:07 ` Soeren Sonnenburg
2007-01-13 1:55 ` Tejun Heo
2007-01-13 7:22 ` Soeren Sonnenburg
2007-01-15 2:21 ` Tejun Heo
2007-01-22 9:04 ` Soeren Sonnenburg
2007-01-22 21:03 ` Henrique de Moraes Holschuh
2007-01-23 6:23 ` Tejun Heo [this message]
2007-01-23 13:10 ` Henrique de Moraes Holschuh
2007-01-24 2:07 ` Tejun Heo
2007-01-24 9:09 ` Soeren Sonnenburg
2007-01-24 15:37 ` Henrique de Moraes Holschuh
2007-01-25 12:56 ` Soeren Sonnenburg
2007-01-25 21:56 ` Henrique de Moraes Holschuh
2007-01-25 21:21 ` Eric D. Mudama
2007-02-05 11:56 ` Tejun Heo
2007-02-05 11:50 ` Tejun Heo
2007-01-23 6:19 ` Tejun Heo
[not found] <fa.pn1gmGiSlhDVMiPyzEEm1A66vcY@ifi.uio.no>
[not found] ` <fa.Od11QHN89ZQ9VkFktF6HvxWuLV0@ifi.uio.no>
[not found] ` <fa.vsuV8EVipw4cXaHgzWpaf0q1pAA@ifi.uio.no>
[not found] ` <fa.8a1kVu4a2ISeaFZcL3migbjZ5N0@ifi.uio.no>
[not found] ` <fa.79JzgEcD2u5B9SYqrw3sr5b+iy8@ifi.uio.no>
[not found] ` <fa.DH50RMz6OHKG0AoGA/cChsCW8Ig@ifi.uio.no>
2007-01-25 0:33 ` Robert Hancock
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=45B5A9C7.5050700@gmail.com \
--to=htejun@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=jeff@garzik.org \
--cc=kernel@nn7.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