Comment 31 for bug 1439780

Revision history for this message
Joshua R. Poulson (jrp) wrote :

We are still seeing some errors.

Here are the results for 15.04 running the upstream 4.1.0-rc8-next built 2015-06-22.
I’m still seeing some error messages, though multipath is at least able to recognize the vFC disks.

root@ubuntu1504:~# multipath -ll
360080e500017c5e2000016bf53d7c0c8 dm-3 IBM,1814 FAStT
size=279G features='1 queue_if_no_path' hwhandler='1 rdac' wp=rw
|-+- policy='round-robin 0' prio=6 status=active
| |- 4:0:1:0 sdd 8:48 active ready running
| `- 4:0:3:0 sdf 8:80 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
  |- 4:0:0:0 sdc 8:32 active ghost running
  `- 4:0:2:0 sde 8:64 active ghost running
360022480252826b1808fb8b00780a6be dm-2 Msft,Virtual Disk
size=4.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 3:0:0:0 sdb 8:16 active ready running

Dmesg messages:
[ 140.678778] device-mapper: table: 252:5: multipath: error getting device
[ 140.678888] device-mapper: ioctl: error adding target to table
[ 140.706106] device-mapper: table: 252:5: multipath: error getting device
[ 140.706282] device-mapper: ioctl: error adding target to table

These 2 items might be specific to the FC or can be ignored, still mentioning them for confirmation:
1. The [current] illegal request is still showing up.
2. “failure for create/reload map” messages still appear.

Should we open a new bug or continue with this one?