Newly added LUN on multipath not recovering from path failure automatically

Solution Verified - Updated -

Issue

  • Newly added LUN on multipath not recovering from path failure automatically

  • Some multipath LUNs are not logging any multipath event even when there is a storage disconnection and other LUNs are reporting errors.

  • After fixing Storage connectivity some multipath devices still shows failed path until run multipath command.

It can look as below:

VV_MB_ORA04_LIN_SPLEX02_UAT (36003ve00000000000000wq000ta58z) dm-26 ,
size=700G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='round-robin 0' prio=0 status=enabled
  |- #:#:#:#  -    #:#    failed undef unknown
  |- #:#:#:#  -    #:#    failed undef unknown
  |- #:#:#:#  -    #:#    failed undef unknown
  |- #:#:#:#  -    #:#    failed undef unknown
  |- #:#:#:#  -    #:#    failed undef unknown
  `- #:#:#:#  -    #:#    failed undef unknown

Environment

  • Red Hat Enterprise Linux

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