All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Shane Huang <Shane.Huang@amd.com>, linux-ide@vger.kernel.org
Subject: Re: Questions about SATA hotplug in linux 2.6
Date: Fri, 26 Oct 2007 11:56:27 +0900	[thread overview]
Message-ID: <4721575B.70706@gmail.com> (raw)
In-Reply-To: <472153D3.2020102@garzik.org>

Jeff Garzik wrote:
> 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.

To add a bit, libata hotplug has grace time of at least 15secs.  If the
same device is plugged out and then plugged in in that time, libata
considers that the device and/or connection has suffered transient
failure and assumes it's the same device and there's no modification to
its content.

This means that if you disconnect a harddrive, write to it and then
connect it back in the grace period corruption will occur.  It will be
fun to have some sort of competition to actually do this.  :-)

>> 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.

Yeah, using LABEL and/or UUID is a good idea.  In the future, it will be
nice to have persistent block device name as netdevices do.

-- 
tejun

  reply	other threads:[~2007-10-26  2:56 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
2007-10-26  2:56       ` Tejun Heo [this message]
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=4721575B.70706@gmail.com \
    --to=htejun@gmail.com \
    --cc=Shane.Huang@amd.com \
    --cc=jeff@garzik.org \
    --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 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.