From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Gal Rosen <galr@storwize.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>, linux-scsi@vger.kernel.org
Subject: RE: SCSI device rescan, detection of disconnected device,or switched devices.
Date: Fri, 01 Aug 2008 09:29:05 -0500 [thread overview]
Message-ID: <1217600945.3347.10.camel@localhost.localdomain> (raw)
In-Reply-To: <0C22B6EFEE0DBB4A9F9F3801E8790B3A732C0C@swdc2.storwiz.com>
On Thu, 2008-07-31 at 21:52 +0300, Gal Rosen wrote:
> It won't change the device identification of the existing 10 LUNs, but
> it will report UA of "Power on, reset, or bus device reset occured",
> then I can send read capacity command.
Sending the same email four times doesn't help ... it likely got eaten
by linux-scsi each time because you sent a mixed text/html message ...
the lists only like plain text
But the point is that what happens is highly array dependent ... some
will change the id some won't. There's nothing we can say for certain
without having knowledge of the array, which really belongs in policy
somewhere.
James
>
> -----Original Message-----
> From: James Bottomley [mailto:James.Bottomley@HansenPartnership.com]
> Sent: Thu 7/31/2008 7:20 PM
> To: Gal Rosen
> Cc: Stefan Richter; linux-scsi@vger.kernel.org
> Subject: Re: SCSI device rescan, detection of disconnected device,or
> switched devices.
>
> On Thu, 2008-07-31 at 19:09 +0300, Gal Rosen wrote:
> > On Thu, 2008-07-31 at 09:15 -0500, James Bottomley wrote:
> > > Oh ... you're not really talking about hotplug, which is why
> everyone is
> > > confused. Hotplug is when you add or remove something from the
> bus.
> > > What you've done is reconfigure the array.
> > >
> > > 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).
> > >
> >
> > ?Why? if I keep a mapping between sg devices and device id (Inquiry
> page
> > 0x83) then I have all the data.
>
> No we don't, it depends on array policy. Most arrays when told to
> take
> 10% of space from 10 luns and create a new one won't change the WWN of
> the existing 10 LUNS, so we have no idea what just happened or what we
> should do about it (incidentally, this is an example of a
> reconfiguration you probably wanted to do offline anyway).
>
> James
>
next prev parent reply other threads:[~2008-08-01 14:29 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
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 ` James Bottomley [this message]
2008-07-31 17:51 ` SCSI device rescan, detection of disconnected device,or " 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=1217600945.3347.10.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=galr@storwize.com \
--cc=linux-scsi@vger.kernel.org \
--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