From: Kaushik Datta <kdatta@npd.hcltech.com>
To: rabeeh@galileo.co.il
Cc: linux-scsi@vger.kernel.org, kdatta@npd.hcltech.com
Subject: Re: Hot plugging a disk in runtime
Date: Mon, 20 May 2002 17:11:50 +0530 [thread overview]
Message-ID: <3CE8E0FE.EF3FA868@npd.hcltech.com> (raw)
In-Reply-To: E179lnL-0005Re-00@the-village.bc.nu
A small cut'n paste from man proc !
scsi This is a listing of all SCSI devices known to the kernel. The
listing is similar to the one seen during bootup. scsi currently
supports only the add-single-device command which allows root to
add a hotplugged device to the list of known devices.
An echo 'scsi add-single-device 1 0 5 0' > /proc/scsi/scsi will
cause host scsi1 to scan on SCSI channel 0 for a device on ID 5 LUN
0. If there is already a device known on this address or the
address is invalid an error will be returned.
Alan Cox wrote:
> > 1.. How is it possible to signal SCSI mid-layer (or other layers) of a
> > presence of a newly hot-plugged disk ?
>
> aacraid is one example that does this, but via its config tools.
>
> > 2.. Can an adapter's device driver trigger SCSI subsystem to scan
> > channels for new LUNs / Targets ?
>
> It is designed so user space can do so - so yes
>
> > 3.. Is this can be handled in a kernel level ? is there a user space
> > application that can be triggered to start scanning adapters (obviously
> > through SCSI subsystem) and registering new LUNs / Targets etc... ?
>
> echo "scsi-add-single-device a b c d" /proc/scsi/scsi
>
To be precise :
echo 'scsi add-single-device a b c d ' > /proc/scsi/scsi
Thanks,
Kaushik
>
> if I remember it right
>
> Alan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-05-20 11:41 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 [this message]
2002-05-20 12:24 ` Rabeeh Khoury
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=3CE8E0FE.EF3FA868@npd.hcltech.com \
--to=kdatta@npd.hcltech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rabeeh@galileo.co.il \
/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