lvmpersist

Start PR on all PVs in a VG with a local key (exclusive access by default)

$ lvmpersist start --ourkey [0x1234abcd] --vg [vg_name]

$ lvmpersist start --ourkey [0x1234abcd] --access sh --vg [vg_name]

$ lvmpersist stop --ourkey [0x1234abcd] --vg [vg_name]

$ lvmpersist start --ourkey [0xmy_key] --removekey [0xother_key] --vg [vg_name]

$ lvmpersist remove --ourkey [0xmy_key] --removekey [0xother_key] --vg [vg_name]

$ lvmpersist read --vg [vg_name]

$ lvmpersist start --ourkey [0x1234abcd] --device [/dev/sdX] --device [/dev/mapper/mpathY]

lvmpersist command [options]

lvmpersist manages SCSI persistent reservations (PR) on block devices used as LVM physical volumes. Persistent reservations prevent multiple hosts from simultaneously accessing shared storage, protecting against data corruption in clustered or failover configurations.
The tool can establish exclusive reservations (one host owns access) or shared reservations (multiple hosts coordinate access). Keys identify each host, and reservations can be preempted if a host fails or needs to be forcibly removed.
Common use cases include SAN-based clusters, high-availability failover pairs, and shared storage environments where fencing is required.

start

Register a key and create a persistent reservation

Release reservation and unregister the key

Remove another host's key from devices

Display registered keys and current reservations

The local host's reservation key (hexadecimal)

Another host's key to preempt or remove

Operate on all physical volumes in the specified volume group

Operate on a specific device (can be repeated)

Reservation type: ex (exclusive) or sh (shared)

Requires SCSI devices that support persistent reservations (SCSI-3 PR). Not all storage arrays implement PR identically; test in your environment. Improper use can cause data loss in shared storage environments. Requires root privileges.

lvm(8), sg_persist(8), vgchange(8), lvmlockd(8)