* qla2xxx behavior with changing volumes
@ 2007-09-19 4:12 Sean Bruno
2007-09-21 16:12 ` Vladislav Bolkhovitin
0 siblings, 1 reply; 3+ messages in thread
From: Sean Bruno @ 2007-09-19 4:12 UTC (permalink / raw)
To: linux-scsi
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.
Sean
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: qla2xxx behavior with changing volumes
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
0 siblings, 1 reply; 3+ messages in thread
From: Vladislav Bolkhovitin @ 2007-09-21 16:12 UTC (permalink / raw)
To: Sean Bruno; +Cc: linux-scsi
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.
Vlad
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: qla2xxx behavior with changing volumes
2007-09-21 16:12 ` Vladislav Bolkhovitin
@ 2007-09-21 16:59 ` Vladislav Bolkhovitin
0 siblings, 0 replies; 3+ messages in thread
From: Vladislav Bolkhovitin @ 2007-09-21 16:59 UTC (permalink / raw)
To: Sean Bruno; +Cc: linux-scsi
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-09-21 16:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox