How can I unfence new storage devices that were just added to a RHEL 6 High Availability cluster with fence_scsi?

Solution In Progress - Updated -

Issue

  • When adding a disk to a RHEL 5 cluster with fence_scsi we use to issue a service scsi_reserve restart, on each node, after the online storage rescan and the configuration of the new luns as pv of a clustered vg. Doing so ensures that the proper keys are placed on the disks added to the configuration and keeps fencing working.
    We have noticed that in RHEL 6 scsi_reserve is no more provided as a service or as an init script. What is the proper way to ensure the keys are placed on the new luns?
  • How do I add new devices to a cluster when using fence_scsi?
  • How do I unfence storage devices added to a cluster after it was already running?
  • Can I register and reserve new storage devices in my cluster without restarting any of the nodes?

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • One or more fencedevices or stonith devices configured to use agent fence_scsi
  • New shared storage devices added to the cluster after nodes are already joined as members

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