From: Tejun Heo <htejun@gmail.com>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: 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:19:45 +0900 [thread overview]
Message-ID: <45B5A901.5050309@gmail.com> (raw)
In-Reply-To: <1169456682.2901.18.camel@localhost>
Soeren Sonnenburg wrote:
> OK, how about this (please especially check the non SIL part):
>
> SATA Hotplug from the User Side
>
> - For SIL3114 and SIL3124 you don't have to run any commands at all. It
ahci and ck804 flavor of sata_nv's can do hotplug without user
assistance too.
[--snip--]
> - For other chipsets one in addition to stop using the device before
> unplugging has to call scsiadd -r to fully remove it, e.g. in the
> following example the disk on scsi host 3 channel 0 id 0 lun 0 will be
> removed, then on reinserting a disk call scsiadd -s :
>
> # scsiadd -p
>
> Attached devices:
> Host: scsi2 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: ST3400832AS Rev: 3.01
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi3 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: ST3400620AS Rev: 3.AA
> Type: Direct-Access ANSI SCSI revision: 05
>
> # scsiadd -r 3 0 0 0
> # scsiadd -s
Doing the above might not be such a good idea on drivers which don't
implement new EH yet. Those are sata_mv, sata_promise (getting there)
and sata_sx4.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-01-23 6:20 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
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 [this message]
[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=45B5A901.5050309@gmail.com \
--to=htejun@gmail.com \
--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 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.