What is the reason multipath daemon reported "multipathd:asm!.asm_ctl_vmb" or "multipathd: ofsctl: failed to get path uid" in message log ?

Solution Verified - Updated -

Issue

  • What is the reason multipath daemon reported multipathd: asm!.asm_ctl_vmb in messages logs?

    multipathd: asm!.asm_ctl_vbg3: add path (uevent) 
multipathd: asm!.asm_ctl_vbg3: failed to store path info 
multipathd: uevent trigger error
multipathd: ofsctl: add path (uevent)
multipathd: ofsctl: failed to get path uid

    or

    # multipath -ll
:
asm/.asm_ctl_spec: No fc_host device for 'host-1'
asm/.asm_ctl_vbg0: No fc_host device for 'host-1'
:

Environment

  • Red Hat Enterprise Linux (RHEL) 5, 6, 7, 8
  • device-mapper-multipath
  • Oracle ASM
  • Exceptions:
    • device-mapper-multipath-0.8.4-2.el8 and later
      • Starting in the 0.8.4-2.el8 (RHEL 8) version of multipath, the default blacklist was changed to be devnode "!^(sd[a-z]|dasd[a-z]|nvme[0-9])". This means only scsi, dasd, and nvme devices by default will be allowed to be used for multipath devices. This thus blacklists asm, ofsctl, and oracleafd devices. Other device types can be manually added using the blacklist_exceptions clause within multipath.conf if, or when, needed. See "Fixes" under Errata: RHEA-2020:4540 for additional details.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content