From: James Bottomley <James.Bottomley@steeleye.com>
To: "Infante, Jon" <Jon.Infante@Emulex.Com>
Cc: Martin Peschke3 <MPESCHKE@de.ibm.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: RE: How to resurrect offlined SCSI devices?
Date: 26 May 2004 11:55:15 -0500 [thread overview]
Message-ID: <1085590517.2116.439.camel@mulgrave> (raw)
In-Reply-To: <8D43EFD7CCBDB24980134BE078C227E704E37B0A@xcm.emulex.com>
On Wed, 2004-05-26 at 11:17, Infante, Jon wrote:
> Wouldn't it be acceptable for the lldd to call scsi_scan_host() at this
> point to force a scsi mid layer rescan of the devices attached to the hba?
> In a fibre channel environment a device can disappear for a long period of
> time, then come back. The driver knows exactly when it comes back and should
> be able to tell the scsi layer.
Well, only if the LLD previously did a remove of the device, which I
don't think it will have done.
I'd really like to see all fibre events (like loop up/down, device
add/remove) handled inside the FC transport class. From there, it
probably still make sense to use hotplug as the mechanism for importing
user policy.
James
next prev parent reply other threads:[~2004-05-26 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 16:17 How to resurrect offlined SCSI devices? Infante, Jon
2004-05-26 16:55 ` James Bottomley [this message]
2004-05-26 17:15 ` Mike Anderson
2004-05-26 17:26 ` Mike Christie
2004-05-26 17:48 ` Mike Anderson
2004-05-26 17:37 ` James Bottomley
2004-05-26 18:02 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2004-05-27 20:05 Martin Peschke3
2004-05-27 20:04 Martin Peschke3
2004-05-26 16:48 Salyzyn, Mark
2004-05-26 15:04 Martin Peschke3
2004-05-26 15:11 ` James Bottomley
2004-05-26 13:14 Martin Peschke3
2004-05-26 14:45 ` James Bottomley
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=1085590517.2116.439.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Jon.Infante@Emulex.Com \
--cc=MPESCHKE@de.ibm.com \
--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 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.