When using fence_scsi with multipath devices and specifying a "devices" attribute in RHEL, reservation conflicts are logged

Solution Verified - Updated -

Issue

  • During some cluster test we have seen some entries in the log file that need our attention:
Feb 11 19:43:48 node2 kernel: sd 2:0:2:6: [sdh] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
Feb 11 19:43:48 node2 kernel: sd 2:0:2:6: [sdh] CDB: Write(10): 2a 00 42 87 08 00 00 04 00 00
Feb 11 19:43:48 node2 kernel: sd 2:0:2:6: reservation conflict
Feb 11 19:43:48 node2 kernel: end_request: critical nexus error, dev sdh, sector 1116147712
  • We have configured the fence_scsi to be used as fencing device for this multipathed device but we get reservation conflicts:
  <fencedevice agent="fence_scsi" name="scsi_node1" devices="/dev/disk/by-id/scsi-3600c0ff00013e0bef982e94f01000000"/>
  <fencedevice agent="fence_scsi" name="scsi_node2" devices="/dev/disk/by-id/scsi-3600c0ff00013e0bef982e94f01000000"/>

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • One or more nodes configured with a fencedevice using the fence_scsi agent in /etc/cluster/cluster.conf
    • The devices attribute is specified for the fence_scsi-based fencedevice. For example:
   <fencedevice agent="fence_scsi" name="scsi_node2" devices="/dev/disk/by-id/scsi-3600c0ff00013e0bef982e94f01000000"/>

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