From: Rabeeh Khoury <rabeeh@galileo.co.il>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Hot plugging a disk in runtime
Date: Mon, 20 May 2002 15:24:52 +0300 [thread overview]
Message-ID: <3CE8EB14.8060803@galileo.co.il> (raw)
In-Reply-To: E179lnL-0005Re-00@the-village.bc.nu
Alan Cox wrote:
>echo "scsi-add-single-device a b c d" /proc/scsi/scsi
>
>
from drivers/scsi/scsi.c : (kernel 2.4.18)
/*
* Usage: echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi
* with "0 1 2 3" replaced by your "Host Channel Id Lun".
* Consider this feature BETA.
* CAUTION: This is not for hotplugging your peripherals. As
* SCSI was not designed for this you could damage your
* hardware !
* However perhaps it is legal to switch on an
* already connected device. It is perhaps not
* guaranteed this device doesn't corrupt an ongoing data transfer.
*/
1.. What is meant by "SCSI was not designed for this ..." ?
2.. SCSI architecture model (SAM-2 at least) does not mention hot-plugging storage device into a running system ; but doing so is a very common task. So, are all the SCSI hot-plug systems in the world are based on proprietry methods of hot-plug ?
3.. What about the naming of /dev/sdxx naming of newly hot-plugged SCSI disk ? which name does it get ? (supposly I'm not using the dev filesystem)
next prev parent reply other threads:[~2002-05-20 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rabeeh@galileo.co.il>
2002-05-20 10:19 ` Hot plugging a disk in runtime Rabeeh Khoury
2002-05-20 11:41 ` Karl Hammar
2002-05-20 11:57 ` Alan Cox
2002-05-20 11:41 ` Kaushik Datta
2002-05-20 12:24 ` Rabeeh Khoury [this message]
2002-05-20 13:14 ` Alan Cox
2002-05-20 14:20 ` James Bottomley
2002-05-21 15:42 ` Michael Clark
2002-05-20 22:33 ` Oliver Xymoron
2002-05-20 16:34 berthiaume_wayne
2002-05-20 17:58 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 18:11 berthiaume_wayne
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=3CE8EB14.8060803@galileo.co.il \
--to=rabeeh@galileo.co.il \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-scsi@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