public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Gal Rosen <galr@storwize.com>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-scsi@vger.kernel.org,
	scst-devel <scst-devel@lists.sourceforge.net>
Subject: Re: SCSI device rescan, detection of disconnected	device,	or	switched devices.
Date: Thu, 31 Jul 2008 21:54:32 +0400	[thread overview]
Message-ID: <4891FC58.6050805@vlnb.net> (raw)
In-Reply-To: <1217521139.3333.14.camel@localhost.localdomain>

James Bottomley wrote:
> On Thu, 2008-07-31 at 19:59 +0400, Vladislav Bolkhovitin wrote:
>> James Bottomley wrote:
>>> Most of the hotplug we do depends on the transport model (because what's
>>> on the transport is changing).  Array reconfiguration has no hotplug
>>> event because SAM-3 has no real way of passing the information
>>> asynchronously.  The best it can do is Unit Attention/reported luns data
>>> has changed (asc=0x3f/ascq=0xe) on the next command.
>>>
>>> The problem is that there's no way to process the event correctly even
>>> when we get it.  All we can do is issue another report LUNS command and
>>> compare.  However, just because it looks like a single LUN disappeared
>>> doesn't mean the others weren't permuted or altered in some way (which
>>> data we cannot get).
>> But why don't do what's possible to do and for what there is complete 
>> information: add new LUN for new LUN and delete deleted LUN for reported 
>> luns data has changed UA? As well as get new capacity for a LU on 
>> capacity data has changed UA after, e.g., new space added to it?
> 
> Well, feel free to submit a patch, but it's an incredible mine field.
> We certainly can't do something that builds a trap for users (as in a
> policy which gets it right 10% of the time and wrong 90% of the time) so
> I'm strongly inclined to feel array reconfiguration is a manual process.
> If you think you can do it online, we don't panic or throw a spanner in
> the works, but we wait until you tell us what you did, but you'd be well
> advised to do it offline.
> 
> The point is that we can't distinguish LUN added from LUN split or space
> reapportioned or something ... even LUN renumbered would be seen as a
> remove followed by an add.

Sure, in cases, where it is impossible based of INQUIRY data 
unambiguously determine that, it's better don't do anything. But in 
cases if it is possible, which is true for most modern devices, it can 
be handled properly.

Vlad


  reply	other threads:[~2008-07-31 17:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 12:32 SCSI device rescan, detection of disconnected device, or switched devices Gal Rosen
2008-07-28 13:10 ` Stefan Richter
2008-07-31  6:57   ` Gal Rosen
2008-07-31  8:34     ` Stefan Richter
2008-07-31 11:48       ` Gal Rosen
2008-07-31 14:15         ` James Bottomley
2008-07-31 15:59           ` Vladislav Bolkhovitin
2008-07-31 16:18             ` James Bottomley
2008-07-31 17:54               ` Vladislav Bolkhovitin [this message]
2008-07-31 16:09           ` Gal Rosen
2008-07-31 16:20             ` James Bottomley
     [not found]               ` <0C22B6EFEE0DBB4A9F9F3801E8790B3A732C0C@swdc2.storwiz.com>
2008-08-01 14:29                 ` SCSI device rescan, detection of disconnected device,or " James Bottomley
2008-07-31 17:51         ` James.Smart
2008-07-31 17:46       ` SCSI device rescan, detection of disconnected device, or " James.Smart

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=4891FC58.6050805@vlnb.net \
    --to=vst@vlnb.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=galr@storwize.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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