From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: SATA hotplug from the user side ?
Date: Fri, 12 Jan 2007 08:57:09 +0100 [thread overview]
Message-ID: <1168588629.5403.7.camel@localhost> (raw)
Dear all,
I'd like to try out SATA hotplugging using a SIL3114. Though I was
harvesting the web, I could not find any useful information how this is
done in practice.
Well I realized that I can still use scsiadd to print and remove
devices, e.g.:
# 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
Is this all one has to do for hotplugging ? I am asking as I find this
in dmesg when I do so (2.6.19.* kernel):
Synchronizing SCSI cache for disk sdb:
ata4.00: disabled
ata4: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0x2 frozen
ata4: hard resetting port
ata4: SATA link down (SStatus 0 SControl 310)
ata4: EH complete
ata4: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0x2 frozen
ata4: hard resetting port
ata4: port is slow to respond, please be patient (Status 0xff)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata4.00: ATA-7, max UDMA/133, 781422768 sectors: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/100
ata4: EH complete
scsi 3:0:0:0: rejecting I/O to dead device
scsi 3:0:0:0: rejecting I/O to dead device
Soeren
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
next reply other threads:[~2007-01-12 7:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 7:57 Soeren Sonnenburg [this message]
2007-01-12 17:04 ` SATA hotplug from the user side ? 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
[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=1168588629.5403.7.camel@localhost \
--to=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