From: James Bottomley <James.Bottomley@steeleye.com>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: How to resurrect offlined SCSI devices?
Date: 26 May 2004 10:11:15 -0500 [thread overview]
Message-ID: <1085584277.2113.189.camel@mulgrave> (raw)
In-Reply-To: <OF8BCC3715.F39A8EBA-ONC1256EA0.00523377-C1256EA0.005351F7@de.ibm.com>
On Wed, 2004-05-26 at 10:04, Martin Peschke3 wrote:
> How does the user know that it is safe?
> What if they just try to bring it online? What is happening in the worst
> case?
> My point is that users probably set the appropriate sys-attribute
> in a "trial and error" fashion, if they think they have got a problem,
> while an lldd might even know better.
The LLD rarely knows why a device was set offline. The user at least
has the logs to look through. Use of the state interface is caveat
emptor anyway.
The way it would work in the scenario you outline: some event indicating
that the device is available is to trigger a hotplug which may take the
action to set the device running again.
Setting devices back on line after a failure is a policy decision that
should not be taken by the LLD.
James
next prev parent reply other threads:[~2004-05-26 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 15:04 How to resurrect offlined SCSI devices? Martin Peschke3
2004-05-26 15:11 ` James Bottomley [this message]
-- 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 16:17 Infante, Jon
2004-05-26 16:55 ` James Bottomley
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
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=1085584277.2113.189.camel@mulgrave \
--to=james.bottomley@steeleye.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox