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:

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

2020-04-20 Thread Oyvind Albrigtsen
Sound like you need to increase the number of journals for your GFS2 filesystem. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/global_file_system_2/s1-manage-addjournalfs Oyvind On 19/04/20 11:03 +, Stefan Sabolowitsch wrote: Andrei, i found this. if i try

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

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

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

2020-04-19 Thread Andrei Borzenkov
16.04.2020 18:58, 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 >

[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) -

Re: [ClusterLabs] unable to start fence_scsi

2016-05-18 Thread Ken Gaillot
On 05/18/2016 05:21 AM, Marco A. Carcano wrote: > Hi Ken, > > by the way I’ve just also tried with pacemaker 1.1.14 (I builded it from > sources into a new RPM) but it doesn’t work > > >> On 18 May 2016, at 11:29, Marco A. Carcano wrote: >> >> Hi Ken, >> >> thank you

Re: [ClusterLabs] unable to start fence_scsi

2016-05-18 Thread Marco A. Carcano
Hi Ken, by the way I’ve just also tried with pacemaker 1.1.14 (I builded it from sources into a new RPM) but it doesn’t work > On 18 May 2016, at 11:29, Marco A. Carcano wrote: > > Hi Ken, > > thank you for the reply > > I tried as you suggested, and now the stonith

Re: [ClusterLabs] unable to start fence_scsi

2016-05-18 Thread Marco A. Carcano
Hi Ken, thank you for the reply I tried as you suggested, and now the stonith devices tries to start but fails. I tried this pcs stonith create scsi fence_scsi pcmk_host_list="apache-up001.ring0 apache-up002.ring0 apache-up003.ring0" pcmk_host_map="apache-up001.ring1=apache-up001.ring0;