System hangs after scanning new lun when trying to enable "HP 3PAR Peer Persistence"

Solution Verified - Updated -

Issue

  • System becomes unresponsive and reports below error messages when Peer Persistence is enabled on HP 3PAR array side.
blk_update_request: critical target error, dev sdX, sector 78910
blk_update_request: critical target error, dev dm-X, sector 12345
  • All the underlying paths of multipath device are grouped in same path group after enabling peer persistence on HP 3PAR array.
testlun (360002ac00000000000000eXYZW) dm-2 3PARdata,VV
size=100G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='round-robin 0' prio=50 status=active
  |- 1:0:0:2 sdd  8:48   active ready running
  |- 1:0:1:2 sdg  8:96   active ready running
  |- 1:0:2:2 sdj  8:144  active ready running
  |- 1:0:5:2 sdm  8:192  active ready running
  |- 2:0:0:2 sdp  8:240  active ready running
  |- 2:0:1:2 sds  65:32  active ready running
  |- 2:0:6:2 sdv  65:80  active ready running
  |- 2:0:7:2 sdy  65:128 active ready running
  |- 1:0:3:2 sdaa 65:160 active ready running
  |- 1:0:4:2 sdac 65:192 active ready running
  |- 1:0:6:2 sdae 65:224 active ready running
  |- 1:0:7:2 sdag 66:0   active ready running
  |- 2:0:2:2 sdai 66:32  active ready running
  |- 2:0:3:2 sdak 66:64  active ready running
  |- 2:0:4:2 sdam 66:96  active ready running
  `- 2:0:5:2 sdao 66:128 active ready running

Environment

  • Red Hat Enterprise Linux
  • HP 3PAR
    • Peer Persistence

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