From: Jeff Garzik <jeff@garzik.org>
To: Shane Huang <Shane.Huang@amd.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Questions about SATA hotplug in linux 2.6
Date: Thu, 25 Oct 2007 22:41:23 -0400 [thread overview]
Message-ID: <472153D3.2020102@garzik.org> (raw)
In-Reply-To: <5CAB7B5D6F8AB84AA868A46B47A50705622EAB@sshaexmb1.amd.com>
Shane Huang wrote:
> 1. If users unplug one SATA HDD(no-root partition) or SATA ODD when
> the system is running, then plug it back to the same SATA port,
> Should the system and SATA HDD/ODD still work well?
Yes.
> 2. How about users plug the SATA HDD/ODD in a different SATA port?
> Should it still work?
Yes.
For all hotplug-aware libata drivers, you should be able to unplug a
SATA device _while_ it is actively reading or writing data, with no ill
effects to the kernel.
You might lose cached and in-flight data of course, and userspace
applications may or may not handle the disappearance of their underlying
filesystem with grace and aplomb :)
But device hotplug should be reliable from a kernel standpoint [assuming
driver support].
> These questions come up when our QA test our SB700 SATA drivers,
> but I don't know the SATA hotplug support in linux 2.6.
> Is there any guy who can give some official confirmation? :-)
The main thing of note with regards to hotplug is that the associated
device (/dev/sdb, /dev/scd0, etc.) may change between plug and unplug.
For example, if you unplug a SATA HDD then plug it back in, the user
might see /dev/sdb disappear, and /dev/sdd appear -- even if it is the
exact same HDD, on the exact same port.
Jeff
next prev parent reply other threads:[~2007-10-26 2:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 8:14 [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks, V2 David Miller
2007-10-25 8:24 ` [PATCH 0/5]: " Jeff Garzik
2007-10-26 2:27 ` Questions about SATA hotplug in linux 2.6 Shane Huang
2007-10-26 2:41 ` Jeff Garzik [this message]
2007-10-26 2:56 ` Tejun Heo
2007-12-18 7:29 ` Shane Huang
2007-12-18 9:18 ` Tejun Heo
2007-12-18 10:52 ` Shane Huang
2007-12-20 6:19 ` Tejun Heo
2007-12-20 9:05 ` Shane Huang
2007-12-20 10:43 ` Shane Huang
2007-12-21 7:35 ` Tejun Heo
2007-10-25 18:32 ` [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks, V2 Greg KH
2007-10-25 22:27 ` David Miller
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=472153D3.2020102@garzik.org \
--to=jeff@garzik.org \
--cc=Shane.Huang@amd.com \
--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).