Comment 27 for bug 1032550

The normal state of the disks is as follows:

LUN-DATABASE (36006016061e02e003cf1aca4ae07e211) dm-2 DGC,VRAID
size=200G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=130 status=active
| |- 4:0:0:1 sdg 8:96 active ready running
| `- 3:0:0:1 sdc 8:32 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 4:0:1:1 sdi 8:128 active ready running
  `- 3:0:1:1 sde 8:64 active ready running
LUN-LOGGING (36006016061e02e000286c1adae07e211) dm-1 DGC,VRAID
size=20G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=130 status=active
| |- 4:0:1:0 sdh 8:112 active ready running
| `- 3:0:1:0 sdd 8:48 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 4:0:0:0 sdf 8:80 active ready running
  `- 3:0:0:0 sdb 8:16 active ready running

So one LUN of 20G, another of 200G, both having 4 path's to the SAN.

Today's test started at Dec 21 10:53:44, with this:
ealxs00161 kernel: [62445.130300] qla2xxx [0000:07:00.0]-500b:3: LOOP DOWN detected (2 3 0 0).

It took several up/down sequences to reproduce the problem.