public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Sean Bruno <sean.bruno@dsl-only.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: qla2xxx behavior with changing volumes
Date: Fri, 21 Sep 2007 20:59:53 +0400	[thread overview]
Message-ID: <46F3F889.6010505@vlnb.net> (raw)
In-Reply-To: <46F3ED51.5030703@vlnb.net>

Vladislav Bolkhovitin wrote:
> Sean Bruno wrote:
> 
>> What is the expected behavior when volumes on a SAN change size and LUN
>> ID order?
>>
>> I've noticed that if a volume changes size, leaves the SAN or changes
>> target ID it isn't auto-magically picked up by a 2.6.18 based
>> system(running CentOS 5).
>>
>> If a new target appears on the SAN however, it is noticed and assigned a
>> new drive letter.
> 
> 
> For changes in the volume size the target (SAN) should generate 
> "CAPACITY DATA HAS CHANGED" Unit Attention.
> 
> For changes in the LUN ID order the target should generate "REPORTED 
> LUNS DATA HAS CHANGED" Unit Attention.
> 
> On these notifications initiator is supposed to make the appropriate 
> actions, like rescan the SAN in case of "REPORTED LUNS DATA HAS 
> CHANGED". Unfortunately, Linux just ignores them as well as the majority 
> of other Unit Attentions, hence you have to restart the system or, at 
> least, the corresponding driver to see the changes.

Or, I forgot, do the manual rescan via sysfs "rescan". Sometimes it 
helps too.

> Vlad
> 


      reply	other threads:[~2007-09-21 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  4:12 qla2xxx behavior with changing volumes Sean Bruno
2007-09-21 16:12 ` Vladislav Bolkhovitin
2007-09-21 16:59   ` Vladislav Bolkhovitin [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=46F3F889.6010505@vlnb.net \
    --to=vst@vlnb.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sean.bruno@dsl-only.net \
    /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