LVM-Activate resource used for shared VG fails to start with the error 'The specified vg_access_mode doesn't match the lock_type on VG metadata!'

Solution Verified - Updated -

Issue

  • When configuring LVM-Activate with the options activation_mode=shared and vg_access_mode=lvmlockd we see:
  * cluster_lvm_start_0 on rhel8-node-1.clust 'invalid parameter' (2): call=61, status='complete', exitreason='The specified vg_access_mode doesn't match the lock_type on VG metadata!', last-rc-change='2021-01-26 11:41:58 -05:00', queued=0ms, exec=132ms
  * cluster_lvm_start_0 on rhel8-node-2.clust 'invalid parameter' (2): call=72, status='complete', exitreason='The specified vg_access_mode doesn't match the lock_type on VG metadata!', last-rc-change='2021-01-26 11:41:58 -05:00', queued=0ms, exec=158ms

Environment

  • Red Hat Enterprise Linux Server 8 (with the Resilient Storage Add On)

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