Re: [ClusterLabs] unable to start fence_scsi on a new add node

2020-04-20 Thread Stefan Sabolowitsch
Oyvind, >> Sound like you need to increase the number of journals for your GFS2 >> filesystem. Thanks that was the trick. Thank you for the professional help here. Stefan ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/u

Re: [ClusterLabs] unable to start fence_scsi on a new add node

2020-04-19 Thread Stefan Sabolowitsch
Andrei, i found this. if i try to mount the volume by hand, i get this error message [root@logger log]# mount /dev/mapper/vg_cluster-lv_cluster /data-san mount: mount /dev/mapper/vg_cluster-lv_cluster on /data-san failed: to many users ___ Manage your s

Re: [ClusterLabs] unable to start fence_scsi on a new add node

2020-04-19 Thread Stefan Sabolowitsch
Privjet / Hello Andrei (happy easter to russia) thanks for the tip, which made me even more brought something, but the volume is not mounted now on the new node. [root@elastic ~]# pcs status Cluster name: cluster_elastic Stack: corosync Current DC: elastic-02 (version 1.1.20-5.el7_7.2-3c4c782f70)

[ClusterLabs] unable to start fence_scsi on a new add node

2020-04-16 Thread Stefan Sabolowitsch
Hi there, i have expanded a cluster with 2 nodes with an additional one "elastic-03". However, fence_scsi does not start on the new node. pcs-status: [root@logger cluster]# pcs status Cluster name: cluster_elastic Stack: corosync Current DC: elastic-02 (version 1.1.20-5.el7_7.2-3c4c782f70) - part