Re: [Pacemaker] Anyone using F13 GFS2(Active/Active) ? Yes? Describe your environment please.

. You guide is very good but for F12. > Date: Mon, 13 Sep 2010 15:15:01 +0200 > From: and...@beekhof.net > To: pacemaker@oss.clusterlabs.org > Subject: Re: [Pacemaker] Anyone using F13 GFS2(Active/Active) ? Yes? Describe > your environment please. > > On Thu, Sep 9, 2010 at

[Pacemaker] Anyone using F13 GFS2(Active/Active) ? Yes? Describe your environment please.

After setting up a 2 node active/active GFS2 - Fedora 13 x86_64, i can't use it because of a "kernel BUG at fs/dlm/lock.c242" and my system is up to date. If you had success with a GFS2, even NOT using Fedora 13, could you please describe your environment(Software/Hardware). MotherBoard: Inte

Re: [Pacemaker] kernel BUG at fs/dlm/lock.c:242! after sync of GFS2 (2 node - active/active)

I am updating this post with an info. After stopping the WebFS resource i could create the GFS2 filesystem on the second node so the only difference now from the Cluster from scratch guide is the: 1 - Changed "/dev/drbd/by-res/wwwdata" to "/dev/drbd1" on WebFS. And i still get the error and

[Pacemaker] kernel BUG at fs/dlm/lock.c:242! after sync of GFS2 (2 node - active/active)

After setting up a 2 node cluster following the cluster from scratch guide for Fedora 13 i have to say that GFS2 filesystem (active/active) doesn't work! If the kernel bug described below is not caused by one the modifications i HAD to do following the guide to continue, so Fedora 13 has no ac

[Pacemaker] Can't mkfs.gfs2 on second node of 2

After setup of a 2 node cluster following cluster from scratch guide for fedora 13, i can't create a gfs2 filesystem on my second node. With corosync stopped says "could not stat device /dev/drbd1". When corosync is started and filesystem stopped says "read only filesystem". Any hint?

Re: [Pacemaker] Resync too slow! Cat /proc/drbd shows 240k/s

That is it! Thank you a lot Dan! Date: Mon, 6 Sep 2010 10:27:32 +0300 From: dfri...@streamwide.ro To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] Resync too slow! Cat /proc/drbd shows 240k/s Message body Alisson Landim wrote: Hi. After setup a 2 node cluster

[Pacemaker] Resync too slow! Cat /proc/drbd shows 240k/s

Hi. After setup a 2 node cluster from cluster from scratch guide using Fedora 13 i saw that resync of data is too slow. Cat /proc/drbd shows 240k/s If you look at the cluster from scratch guide here: http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch07s02s03.html

Re: [Pacemaker] Couldn't find device [/dev/drbd/by-res/wwwdata]. Expected /dev/??? to exist

..@linbit.com To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] Couldn't find device [/dev/drbd/by-res/wwwdata]. Expected /dev/??? to exist Message body On 09/03/2010 01:05 PM, Alisson Landim wrote: I was following cluster from scratch guide and everything were fin

Re: [Pacemaker] Couldn't find device [/dev/drbd/by-res/wwwdata]. Expected /dev/??? to exist

Re: [Pacemaker] Couldn't find device [/dev/drbd/by-res/wwwdata]. Expected /dev/??? to exist Message body On 09/03/2010 01:05 PM, Alisson Landim wrote: I was following cluster from scratch guide and everything were fine until i get here: http://www.clusterlabs.org/doc/en-US/P

Re: [Pacemaker] Couldn't find device [/dev/drbd/by-res/wwwdata]. Expected /dev/??? to exist

abs.org Subject: Re: [Pacemaker] Couldn't find device [/dev/drbd/by-res/wwwdata]. Expected /dev/??? to exist Message body On 09/03/2010 01:05 PM, Alisson Landim wrote: I was following cluster from scratch guide and everything were fine until i get here: http://ww

[Pacemaker] Couldn't find device [/dev/drbd/by-res/wwwdata]. Expected /dev/??? to exist

I was following cluster from scratch guide and everything were fine until i get here: http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s05.html The command: grep ERROR: /var/log/messages | grep -v unpack_resources Says: Couldn't find device [/dev/drbd/by-res/ww