public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ewan Milne <emilne@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: device-mapper development <dm-devel@redhat.com>,
	linux-scsi@vger.kernel.org,
	Christophe Varoqui <christophe.varoqui@opensvc.com>
Subject: Re: [dm-devel] ALUA - rescan device capacity on zero sized block devices
Date: Fri, 12 Jun 2015 12:59:57 -0400	[thread overview]
Message-ID: <1434128397.22842.102.camel@localhost.localdomain> (raw)
In-Reply-To: <1434122272.22842.80.camel@localhost.localdomain>

On Fri, 2015-06-12 at 11:17 -0400, Ewan Milne wrote:
> There's an interesting, somewhat-related issue I've come across with
> iSCSI storage, when an event happens while the connection is not
> established (i.e. link down, or logged out for some reason).  The T10
> spec says that UAs are supposed to be reported on the I-T nexuses,

... but if the I-T nexus doesn't exist when the event occurs, it
doesn't get reported when the nexus is re-established, and it does
not seem like there is any requirement to do so.


      reply	other threads:[~2015-06-12 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1887682221.152035.1428939145196.JavaMail.zimbra@kangaroot.net>
     [not found] ` <552C008A.9070201@sandisk.com>
     [not found]   ` <987831457.156812.1428996031503.JavaMail.zimbra@kangaroot.net>
     [not found]     ` <552CCC77.9040703@suse.de>
     [not found]       ` <552CE2C2.8000809@sandisk.com>
     [not found]         ` <CABr-GnefEhc_dOKs360Hox7asbvO5qN8BqPczqC+V8CQ6Myh8w@mail.gmail.com>
     [not found]           ` <55349580.1040205@suse.de>
2015-06-10 15:02             ` [dm-devel] ALUA - rescan device capacity on zero sized block devices Ewan Milne
2015-06-11  5:52               ` Hannes Reinecke
2015-06-12 15:17                 ` Ewan Milne
2015-06-12 16:59                   ` Ewan Milne [this message]

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=1434128397.22842.102.camel@localhost.localdomain \
    --to=emilne@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --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