- Original Message -
> From: "Jefferson Carlos Machado"
> To: "The Pacemaker cluster resource manager" ,
> gluster-us...@gluster.org
> Sent: Friday, February 7, 2014 11:55:37 AM
> Subject: [Pacemaker] [Gluster-users] Pacemaker and GlusterFS
>
> Hi,
>
> How the best way to create a r
Hi,
How the best way to create a resource filesystem managed type glusterfs?
Regards,
___
Gluster-users mailing list
gluster-us...@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users
__
07.02.2014 14:22, Asgaroth wrote:
...
>
> Thanks for the explanation, this is interresting for me as I need a
> volume manager in the cluster to manager the shared file systems in case
> I need to resize for some reason. I think I may be coming up against
> something similar now that I am testing
On 06/02/2014 04:30, Nikita Staroverov wrote:
Why do you need clvmd as a cluster resource? If you start clvmd
outside of a cluster your problem will be no problem at all.
I was running it under pacemaker because it is a neat way of seeing
dependant services. When I remove dlm/clvmd from pacema
On 06/02/2014 05:52, Vladislav Bogdanov wrote:
Hi,
I bet your problem comes from the LSB clvmd init script.
Here is what it does do:
===
...
clustered_vgs() {
${lvm_vgdisplay} 2>/dev/null | \
awk 'BEGIN {RS="VG Name"} {if (/Clustered/) print $1;}'
}
clustered_active_lvs()
On 05/02/2014 18:57, Никита Староверов wrote:
It seems to me, clvmd can't answer to pacemaker monitor operation in
30 sec because it is also locked by dlm.
You don't need clvmd and dlvm resources on cman-based clusters. clvm
can simply start after cman. both dlvm and fenced are configured by
cman
Its somewhat inferred in the description of cluster-recheck-interval
cluster-recheck-interval = time [15min]
Polling interval for time based changes to options, resource
parameters and constraints.
The Cluster is primarily event driven, however the configuratio
