two paths remain failed on DS6800 after code upgrade
Hello,
I have a test server connected to an IBM DS6800 storage.
It is a blade bl480c with two qlogic hbas, connected to 2 fc-switches.
RH EL 4.6 x86_64 installed (kernel 2.6.9-67.ELsmp)
device-mapper-1.02.21-1.el4
device-mapper-multipath-0.4.5-27.RHEL4
In boot messages I have for the hbas:
qla2400 0000:0c:00.0: Found an ISP2432, irq 185, iobase 0xffffff000001c000
QLogic Fibre Channel HBA Driver: 8.01.07-d4
QLogic QMH2462 - SBUS to 2Gb FC, Dual Channel
On the storage I have access to two luns, so that in total I get 8 paths and disks from sda to sdh.
In multipath I'm using default os install config for ds6800 (storage 1750500)
so it should be:
#***** device {
#************** vendor***************** "IBM"
#************** product**************** "1750500"
We had a code update for the storage, and so I wanted to test the multipath behaviour.
It was made in concurrent mode.
I get a first path-change whithout problems, probably when fisrt controller was updated.
mpath1:
\_ round-robin 0 [enabled]
**** \_
0:0:0:1 sdb 8:16* [failed]
**** \_ 1:0:0:1 sdf 8:80* [failed]
and
mpath0:
\_ round-robin 0 [enabled]
**** \_ 0:0:0:0 sda 8:0** [failed]
**** \_ 1:0:0:0 sde 8:64* [failed]
while the other two path group remained active.
At the end of upgrade, probably with the second controller update, I get the situation below.
while other servers with windows and Linux (using sdd) came back with all paths, this server retains two paths in failed state:
*Product revision level: .441
*Unit serial number: 68778501600
Any help to get up the paths?
Could it help a scsi rescan? What should be the correct command in this case?
The system is operational and without interruption on disk acces for the users, but I don't understand why the paths don't come up again...
Thanks in advance for help or suggestions.
Gianluca
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
06-13-2008, 04:22 PM
"Gianluca Cecchi"
two paths remain failed on DS6800 after code upgrade
It seems I solved the problem removing the disks and then adding them, with the commands:
for sdc
remove:
echo "1" > /sys/class/scsi_host/host0/device/target0:0:1/0:0:1:0/delete
To reregister the disk with the kernel used the command:
echo "0 1 0" > /sys/class/scsi_host/host0/scan
To reregister the disk with the kernel used the command:
echo "0 1 1" > /sys/class/scsi_host/host0/scan
In general
deregister
echo "1" > /sys/class/scsi_host/hostH/device/targetH:B:T/H:B:T:L/delete
To reregister the disk with the kernel:
echo "B T L" > /sys/class/scsi_host/hostH/scan
Device name persistence not granted. In my case
sdc --> sdi
sdd --> sdd
All operations were transparent and with no downtime.
I also removed other disks and then readded (also during I/O using them) and I have to say that multipath seems very robust.
Thanks to the developers.
HIH for others.
Still I don't understand why* it was before unable to reinstate the path.
Gianluca*
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel