*
>
> ** **
>
> Maurits
>
> ** **
>
> ** **
>
> *Van:* drbd-user-boun...@lists.linbit.com [mailto:
> drbd-user-boun...@lists.linbit.com] *Namens *Zohair Raza
> *Verzonden:* woensdag 31 oktober 2012 9:51
> *Aan:* Felix Frank
> *CC:* drbd-user@lists.linbit.co
; But it has nothing to do with drbd. The drbd 8.3 branch is very
> > mature I do not know if this is the same for glusterfs.
> >
> > Best regards,
> >
> > Maurits
> >
> >
> > Van: drbd-user-boun...@lists.linbit.com [mailto:
> drbd-user-boun...@lists.
On 10/31/2012 10:53 AM, Zohair Raza wrote:
> Hi.
>
> Right now just simulating on vmware, have to setup on real hardware later.
Well yes, VMware based fencing won't work in production then.
I'd advise to try with IPMI-enabled hardware and go from there, but do
mind the caveats as laid out by La
Hi.
Right now just simulating on vmware, have to setup on real hardware later.
Regards,
Zohair Raza
On Wed, Oct 31, 2012 at 1:43 PM, Felix Frank wrote:
> Hi,
>
> so you're building an active-active cluster via WAN? That requires guts.
>
> Do the services run on physical hardware or in virtu
The drbd 8.3 branch is very
> mature I do not know if this is the same for glusterfs.
>
> Best regards,
>
> Maurits
>
>
> Van: drbd-user-boun...@lists.linbit.com
> [mailto:drbd-user-boun...@lists.linbit.com] Namens Zohair Raza
> Verzonden: woensdag 31 oktober 2012 9
Hi,
so you're building an active-active cluster via WAN? That requires guts.
Do the services run on physical hardware or in virtual machines? In the
latter case, it should be quite possible to implement fencing through
the virtualization layer (vmware was mentioned earlier in this thread,
but not
rfs.
Best regards,
Maurits
Van: drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] Namens Zohair Raza
Verzonden: woensdag 31 oktober 2012 9:51
Aan: Felix Frank
CC: drbd-user@lists.linbit.com
Onderwerp: Re: [DRBD-user] GFS2 freezes
So If I don't have real fencing d
de
-Oorspronkelijk bericht-
Van: drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] Namens Felix Frank
Verzonden: woensdag 31 oktober 2012 9:31
Aan: drbd-user@lists.linbit.com
Onderwerp: Re: [DRBD-user] GFS2 freezes
On 10/31/2012 12:02 AM, Lars Ellenberg wrote:
>
So If I don't have real fencing device, I can't get a cluster?
My requirement is to synchronized two Samba boxes between remote locations,
I can't use rsync because of bandwidth consumption and system processing
each time it will run it will go through each file and see if it is synced
or not.
Wh
On 10/31/2012 12:02 AM, Lars Ellenberg wrote:
>>> Manual fencing is not in any way supported. You must be able to call
>>> > > 'fence_node ' and have the remote node reset. If this doesn't
>>> > > happen, your fencing is not sufficient.
>> > fence_node doesn't work for me
>> >
>> > fence_node nod
On Tue, Oct 30, 2012 at 10:03:09PM +0400, Zohair Raza wrote:
> On Tue, Oct 30, 2012 at 7:58 PM, Digimer wrote:
> > On 10/30/2012 05:43 AM, Zohair Raza wrote:
> > > I have rebuild the setup, and enabled fencing
> > >
> > > Manual fencing (fence_ack_manual) works okay when I fence one a dead
> > > n
fence_node doesn't work for me
fence_node node2 says
fence node2 failed
Regards,
Zohair Raza
On Tue, Oct 30, 2012 at 7:58 PM, Digimer wrote:
> Manual fencing is not in any way supported. You must be able to call
> 'fence_node ' and have the remote node reset. If this doesn't
> happen, your
Manual fencing is not in any way supported. You must be able to call
'fence_node ' and have the remote node reset. If this doesn't
happen, your fencing is not sufficient.
On 10/30/2012 05:43 AM, Zohair Raza wrote:
> I have rebuild the setup, and enabled fencing
>
> Manual fencing (fence_ack_manu
I have rebuild the setup, and enabled fencing
Manual fencing (fence_ack_manual) works okay when I fence one a dead node
from command line but it is not doing automatically
Logs:
Oct 30 12:05:52 node1 kernel: dlm: closing connection to node 2
Oct 30 12:05:52 node1 fenced[1414]: fencing node node2
Maurits van de Lande
>
>
>
>
>
>
>
> *Van:*drbd-user-boun...@lists.linbit.com
> [mailto:drbd-user-boun...@lists.linbit.com] *Namens *Zohair Raza
> *Verzonden:* maandag 29 oktober 2012 11:03
> *Aan:* drbd-user@lists.linbit.com
> *Onderwerp:* [DRBD-u
When a node stops responding, it can not be assumes to be dead. It has
to be put into a known state, and that is what fencing does. Disabling
fencing is like driving without a seatbelt.
Ya, it'll save you a bit of time at first, but the first time you get a
split-brain, you are going right through
Hi,
On 10/29/2012 04:19 PM, Zohair Raza wrote:
> It worked for me with fencing disabled, Now I still have access to my
> gfs2 partition when one node is unplugged
oh, it works, but as soon as you have a (short) connectivity issue
between your DRBD nodes, your cluster ends up in a split brain situ
Hi,
What are disadvantages of disabling fencing
It worked for me with fencing disabled, Now I still have access to my gfs2
partition when one node is unplugged
I have only this in cluster.conf
and this in drbd.conf
global { us
Hi,
On 10/29/2012 02:43 PM, Maurits van de Lande wrote:
> I think that adding the following option to the dlm section in cluster.conf
>
> enable_fencing="0"
>
> might solve this problem. (but I have not tested this) This will disable
> fencing.
...but from what I remember from training and othe
rds,
>
> ** **
>
> Maurits van de Lande
>
> ** **
>
> ** **
>
> ** **
>
> *Van:* drbd-user-boun...@lists.linbit.com [mailto:
> drbd-user-boun...@lists.linbit.com] *Namens *Zohair Raza
> *Verzonden:* maandag 29 oktober 2012 11:03
> *Aan:* drbd-user@
fencing.
Or you can setup fencing.
Best regards,
Maurits van de Lande
Van: drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] Namens Zohair Raza
Verzonden: maandag 29 oktober 2012 11:03
Aan: drbd-user@lists.linbit.com
Onderwerp: [DRBD-user] GFS2 freezes
Hi,
I ha
Hi,
I have setup a Primary/Primary cluster with GFS2.
All works good if I shut down any node regularly, but when I unplug power
of any node, GFS freezes and I can not access the device.
Tried to use http://people.redhat.com/lhh/obliterate
this is what I see in logs
Oct 29 08:05:41 node1 kernel
22 matches
Mail list logo
