From: Mike Christie <michaelc@cs.wisc.edu>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Menny_Hamburger@Dell.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sd: sd should not modify read capacity, cache type or write protect flag on rescan when there is a transport error
Date: Wed, 09 Mar 2011 18:01:22 -0600 [thread overview]
Message-ID: <4D7814D2.8090101@cs.wisc.edu> (raw)
In-Reply-To: <1299594151.2476.10.camel@mulgrave.site>
On 03/08/2011 08:22 AM, James Bottomley wrote:
> On Tue, 2011-03-08 at 09:30 +0000, Menny_Hamburger@Dell.com wrote:
>> Another totally different way may be to have the SCSI layer send some
>> notification (unknown property, needs rescan) that could be picked up
>> and handled by the transport layer.
>
> This is the hotplug I suggested, isn't it?
>
Yeah.
Menny, I think you can just do the scsi/iscsi_rescan_target option I
suggested in my pseudo patch where when the transport comes back online
the iscsi class calls some helper scsi function that calls
scsi_rescan_device for each device on the target, so proper values are
picked up.
next prev parent reply other threads:[~2011-03-10 0:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 14:21 [PATCH] sd: sd should not modify read capacity, cache type or write protect flag on rescan when there is a transport error Menny_Hamburger
2011-02-27 14:51 ` Matthew Wilcox
2011-02-28 15:34 ` James Bottomley
2011-03-08 9:30 ` Menny_Hamburger
2011-03-08 14:22 ` James Bottomley
2011-03-10 0:01 ` Mike Christie [this message]
2011-03-10 8:49 ` Menny_Hamburger
2011-03-10 20:28 ` Mike Christie
2011-03-24 11:10 ` Menny_Hamburger
-- strict thread matches above, loose matches on Subject: below --
2011-02-27 14:58 Menny_Hamburger
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=4D7814D2.8090101@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@suse.de \
--cc=Menny_Hamburger@Dell.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