From robert.hoo.linux at gmail.com Sat Jul 5 04:33:01 2025 From: robert.hoo.linux at gmail.com (Robert Hoo) Date: Sat, 5 Jul 2025 12:33:01 +0800 Subject: [ClusterLabs] Q: GFS2 setup with pacemaker failed at LVM-activate resource create Message-ID: Hi, I'm trying to setup GFS2 file system on a shared nvme storage, following RHEL's manual Chapter 8. GFS2 file systems in a cluster | Configuring GFS2 file systems | Red Hat Enterprise Linux | 8 | Red Hat Documentation Chap 8. ( https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_gfs2_file_systems/assembly_configuring-gfs2-in-a-cluster-configuring-gfs2-file-systems ) Failed at step 12: pcs resource create sharedlv1 --group shared_vg1 ocf:heartbeat:LVM-activate lvname=shared_lv1 vgname=shared_vg1 activation_mode=shared vg_access_mode=lvmlockd Is it because previous lvcreate step shouldn't "--activate sy"? journal log shows: notice: Transition 7 aborted by operation sharedlv1_monitor_0 'modify' on node2: Event failed notice: Transition 7 action 7 (sharedlv1_monitor_0 on node2): expected 'not running' but got 'ok' DEBUG: sharedlv1 monitor : 0 notice: Result of probe operation for sharedlv1 on node1: ok notice: Transition 7 action 6 (sharedlv1_monitor_0 on node1):expected 'not running' but got 'ok' notice: Transition 7 (Complete=3, Pending=0, Fired=0, Skipped=0, Incomplete=3, Source=/var/lib/pacemaker/pengine/pe-input-52.bz2): Complete error: Resource sharedlv1 is active on 2 nodes (attempting recovery) notice: See https://wiki.clusterlabs.org/wiki/FAQ#Resource_is_Too_Active for more information notice: * Move sharedlv1 ( node1 -> node2 ) error: ... [...] notice: Initiating stop operation sharedlv1_stop_0 on node2 notice: Initiating stop operation sharedlv1_stop_0 locally on node1 notice: Requesting local execution of stop operation for sharedlv1 on node1 [...] -------------- next part -------------- An HTML attachment was scrubbed... URL: