linux-kernel - Re: SATA hotplug from the user side ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45B5A901.5050309@gmail.com>
Date:	Tue, 23 Jan 2007 15:19:45 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Soeren Sonnenburg <kernel@....de>
CC:	Jeff Garzik <jeff@...zik.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: SATA hotplug from the user side ?

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/