If multipathd failed to add a path to the multipath device table. It would not correctly orphan the path. This would cause multipath to treat the path as if it belonged to a multipath device, when it did not

Solution Verified - Updated -

Issue

  • If multipathd failed to add a path to the multipath device table. It would not correctly orphan the path. This would cause multipath to treat the path as if it belonged to a multipath device, when it did not.

    Consequence: Multipathd could keep trying to switch to a non-existent pathgroup if it failed to add a path to the multipath device. Errors similar to below would be seen

Jan 17 01:25:35 hostname kernel: device-mapper: table: 252:9: multipath: error getting device
Jan 17 01:25:35 hostname kernel: device-mapper: ioctl: error adding target to table
Jan 17 01:25:35 hostname multipathd: mpathaaq: failed in domap for addition of new path sdmg
Jan 17 01:25:35 hostname multipathd: mpathaaq: uev_add_path sleep
Feb 17 21:52:21 hostname kernel: device-mapper: multipath: invalid PG number supplied to switch_pg_num
Feb 17 21:52:22 hostname kernel: device-mapper: multipath: invalid PG number supplied to switch_pg_num

Environment

  • Red Hat Enterprise Linux 6
  • lower versions of device-mapper-multipath than device-mapper-multipath-0.4.9-76.el6

  • Red Hat Enterprise Linux7

  • lower versions of device-mapper-multipath than device-mapper-multipath-0.4.9-77.el7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In