Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread su liu
hello digimer, I am happy to tell you that I got the reason why I can not access the LVs on the compute1 node. Because I make a mistake with thc /etc/lvm/lvm.con on the compute1 node. Now it works. Then I would to study how to snapshotting a LV. Thank you! 2016-12-06 14:24 GMT+08:00 su liu

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread su liu
It is the resource configration whthin my pacemaker cluster: [root@controller ~]# cibadmin --query --scope resources

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread su liu
Thank you very much. Because I am new to pacemaker, and I have checked the docs that additional devices are needed when configing stonith, but now I does not have it in my environment. I will see how to config it afterward. Now I want to know how the cluster LVM works. Thank you for your

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread Digimer
On 05/12/16 10:32 PM, su liu wrote: > Digimer, thank you very much! > > I do not need to have the data accessible on both nodes at once. I want > to use the clvm+pacemaker+corosync in OpenStack Cinder. I'm not sure what "cinder" is, so I don't know what it needs to work. > then only a VM need

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread su liu
lvscan result on compute1 node: [root@compute1 ~]# lvscan inactive '/dev/cinder-volumes/volume-1b0ea468-37c8-4b47-a6fa-6cce65b068b5' [1.00 GiB] inherit 2016-12-06 11:32 GMT+08:00 su liu : > Digimer, thank you very much! > > I do not need to have the data accessible on

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread su liu
Digimer, thank you very much! I do not need to have the data accessible on both nodes at once. I want to use the clvm+pacemaker+corosync in OpenStack Cinder. then only a VM need access the LV at once. But the Cinder service which runs on the controller node is responsible for snapshotting the

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread Digimer
On 05/12/16 09:10 PM, su liu wrote: > Thanks for your replay, This snapshot factor will seriously affect my > application. Do you really need to have the data accessible on both nodes at once? To do this requires a cluster file system as well, like gfs2. These all require cluster locking (DLM)

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread su liu
Thanks for your replay, This snapshot factor will seriously affect my application. then, because now I have not a stonith device and I want to verify the basic process of snapshot a clustered LV. I have a more question: After I create a VG: cinder-volumes on controller node, I can see it

Re: [ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread Digimer
On 05/12/16 08:16 PM, su liu wrote: > *Hi all, > > * > *I am new to pacemaker and I have some questions about the clvmd + > pacemaker + corosync. I wish you could explain it for me if you are > free. thank you very much! > > * > *I have 2 nodes and the pacemaker's status is as follows:* > >

[ClusterLabs] [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

2016-12-05 Thread su liu
*Hi all,* *I am new to pacemaker and I have some questions about the clvmd + pacemaker + corosync. I wish you could explain it for me if you are free. thank you very much!* *I have 2 nodes and the pacemaker's status is as follows:* [root@controller ~]# pcs status --full Cluster name: mycluster

[ClusterLabs] Error performing operation: Argument list too long

2016-12-05 Thread Shane Lawrence
I'm experiencing a strange issue with pacemaker. It is unable to check the status of a systemd resource. systemctl shows that the service crashed: [root@xx ~]# systemctl status rsyslog ● rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service;

[ClusterLabs] How to DRBD + Pacemaker + Samba in Active/Passive Cluster?

2016-12-05 Thread Semion Itic
Hello Everybody, How to DRBD + Pacemaker + Samba in Active/Passive Cluster? I have been searching now about many days how to integrate drbd + pacemaker and corosync in a two node active/passive cluster (with Service IP) with SAMBA. And I still don’t unterstand how to to go further after

Re: [ClusterLabs] Antwort: Re: clone resource - pacemaker remote

2016-12-05 Thread Ken Gaillot
On 12/05/2016 09:20 AM, philipp.achmuel...@arz.at wrote: > Ken Gaillot schrieb am 02.12.2016 19:27:09: > >> Von: Ken Gaillot >> An: users@clusterlabs.org >> Datum: 02.12.2016 19:32 >> Betreff: Re: [ClusterLabs] clone resource - pacemaker remote >> >> On

Re: [ClusterLabs] need some help with failing resources

2016-12-05 Thread Ken Gaillot
On 12/05/2016 09:30 AM, Darko Gavrilovic wrote: > On 12/5/2016 10:17 AM, Ken Gaillot wrote: >> On 12/03/2016 05:19 AM, Darko Gavrilovic wrote: >>> Here is the output for that resource.. edited >>> >>> primitive svc-mysql ocf:heartbeat:mysql \ >>> params binary="/usr/bin/mysqld_safe"