Nodes receive "reservation conflict" errors when cluster daemons are stopped manually or when the fence_scsi device is removed from the configuration in a RHEL 5, 6, or 7 High Availability cluster
Issue
- I get "reservation conflict" errors when accessing shared storage devices after stopping the cluster daemons on all nodes.
- The cluster doesn't appear to be removing SCSI reservations from our disks when we stop the cluster
- After stopping the cluster services
cman,clvmd,rgmanager, on a cluster node, the SCSI reservation keys for that node are still present on SAN devices - We've removed the
fence_scsidevice from our cluster configuration because we're switching to a different method, but we still get "reservation conflict" errors on the nodes even after restarting the cluster
Environment
- Red Hat Enterprise Linux (RHEL) 5, 6, or 7 with the High Availability Add On
- Cluster configured to use SCSI Persistent Reservation Fencing (
fence_scsi) in/etc/cluster/cluster.conf
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.