A Self-Fencing resource[1] is one which automatically guarantees exclusive access to its resource. IBM[2]'s ServeRAID[3] controllers, for example, are self-fencing.
Certain other resources (like a DiskReservation[4] resource for example) can be effectively to fence[5] other resources (like the disk they depend on), can also be considered to be self-fencing, since only one such resource can be logically started at a time.
Self-fencing resources are distinct from resources which do not require fencing at all in order to maintain their integrity.
ResourceFencing[6], STONITH[7], NodeFencing[8]
| [1] | http://www.linux-ha.org/resource |
| [2] | http://www.linux-ha.org/IBM |
| [3] | http://www.linux-ha.org/ServeRAID |
| [4] | http://www.linux-ha.org/DiskReservation |
| [5] | http://www.linux-ha.org/fencing |
| [6] | http://www.linux-ha.org/ResourceFencing |
| [7] | http://www.linux-ha.org/STONITH |
| [8] | http://www.linux-ha.org/NodeFencing |
This information provided courtesy of the Linux-HA project at http://linux-ha.org/