SLES 11 and multipath
We try to migrate one of our SLES 10.2 servers to SLES 11 and noticed some serious problems with multipath.
First, there are some tools that are now in a new location and have different Arguments:
getuid_callout "/lib/udev/scsi_id -g -u -d /dev/%n"
This executable is provided by the udev package and is now located under "/lib/udev/" and no longer under "/sbin/". The SLES 11 Documentation is wrong here.
Tools like "/sbin/mpath_prio_hds_modular" are no longer part of the multipath-tools package. I was not able to find them, are they built-in now (/lib/multipath/libpriohds.so)?
Finaly if i run multipath i don't get any mappings at all. If i run "multipath -v5" i see the following error message:
-------------------------8><-----------------------------------------------
Sep 07 10:18:53 | A13-22P413: assembled map [1 queue_if_no_path 0 2 1 round-robin 0 1 1 8:32 1000 round-robin 0 1 1 8:16 1000]
Sep 07 10:18:53 | A13-22P413: set ACT_CREATE (map does not exist)
Sep 07 10:18:53 | A13-22P413: addmap [0 230866944 multipath 1 queue_if_no_path 0 2 1 round-robin 0 1 1 8:32 1000 round-robin 0 1 1 8:16 1000]
Sep 07 10:18:54 | libdevmapper: ioctl/libdm-iface.c(1691): device-mapper: reload ioctl failed: Invalid argument
Sep 07 10:18:54 | A13-22P413: addmap [0 230866944 multipath 1 queue_if_no_path 0 2 1 round-robin 0 1 1 8:32 1000 round-robin 0 1 1 8:16 1000]
Sep 07 10:18:54 | libdevmapper: ioctl/libdm-iface.c(1691): device-mapper: reload ioctl failed: Invalid argument
Sep 07 10:18:54 | A13-22P413: domap (0) failure for create/reload map
Sep 07 10:18:54 | A13-22P413: remove multipath map
Sep 07 10:18:54 | sdb: orphaned
Sep 07 10:18:54 | sdc: orphaned
Sep 07 10:18:54 | unloading hds prioritizer
Sep 07 10:18:54 | unloading const prioritizer
Sep 07 10:18:54 | unloading tur checker
Sep 07 10:18:54 | unloading directio checker
----------------------------8><----------------------------------------
???:
"libdevmapper: ioctl/libdm-iface.c(1691): device-mapper: reload ioctl failed: Invalid argument"
Is it possible that this is still a misconfiguration or is this a bug? For me it looks like a method call with the wrong arguments.
any ideas?
|