[Linux-HA] newbie question

[Andrew Beekhof]

maybe try the drbd mailing list

On Feb 12, 2008, at 4:17 PM, Doug Lochart wrote:

> I have been trying to follow several tutorials simultaneously to try
> and get the most info at one time.  I am just trying to do a simple HA
> solution between 2 servers.  There will be 2 services shared and a 1
> terrabyte partition for data.  I have the pieces installed and mostly
> configured.  I am at the point now where i am bringing up the DRBD
> resource.
>
> First I am running everything on a Centos 5.1 x686_64 with the latest
> rpms of heartbeat and drbd.  (2.1.3-3 and 8.08).
>
> I did the following:
> $  drbdadm create-md r0
>
> this went fine.  then I did
> $  drbdadm up all
>
> I received this output:
> ----
> WARN:
>  You are using the 'drbd-peer-outdater' as outdate-peer program.
>  If you use that mechanism the dopd heartbeat plugin program needs
>  to be able to call drbdsetup and drbdmeta with root privileges.
>
>  You need to fix this with these commands:
>  chgrp haclient /sbin/drbdsetup
>  chmod o-x /sbin/drbdsetup
>  chmod u+s /sbin/drbdsetup
>
>
> WARN:
>  You are using the 'drbd-peer-outdater' as outdate-peer program.
>  If you use that mechanism the dopd heartbeat plugin program needs
>  to be able to call drbdsetup and drbdmeta with root privileges.
>
>  You need to fix this with these commands:
>  chgrp haclient /sbin/drbdmeta
>  chmod o-x /sbin/drbdmeta
>  chmod u+s /sbin/drbdmeta
>
>
> Failure: (133) This would cause a sync-after dependency cycle
> Command 'drbdsetup /dev/drbd0 syncer --set-defaults --create-device
> --rate=10M --after=0 --al-extents=257' terminated with exit code 10
> ---
>
> syslog shows this:
> Feb 12 09:47:05 capestor1 kernel: drbd0: disk( Inconsistent ->  
> Diskless )
> Feb 12 09:47:05 capestor1 kernel: drbd0: drbd_bm_resize called with
> capacity == 0
> Feb 12 09:47:05 capestor1 kernel: drbd0: worker terminated
> Feb 12 09:47:20 capestor1 kernel: drbd0: disk( Diskless -> Attaching )
> Feb 12 09:47:20 capestor1 kernel: drbd0: No usable activity log found.
> Feb 12 09:47:20 capestor1 kernel: drbd0: max_segment_size ( = BIO  
> size ) = 32768
> Feb 12 09:47:20 capestor1 kernel: drbd0: drbd_bm_resize called with
> capacity == 1953042632
> Feb 12 09:47:20 capestor1 kernel: drbd0: resync bitmap: bits=244130329
> words=3814537
> Feb 12 09:47:20 capestor1 kernel: drbd0: size = 931 GB (976521316 KB)
> Feb 12 09:47:21 capestor1 kernel: drbd0: reading of bitmap took 457  
> jiffies
> Feb 12 09:47:21 capestor1 kernel: drbd0: recounting of set bits took
> additional 28 jiffies
> Feb 12 09:47:21 capestor1 kernel: drbd0: 931 GB (244130329 bits)
> marked out-of-sync by on disk bit-map.
> Feb 12 09:47:21 capestor1 kernel: drbd0: disk( Attaching ->  
> Inconsistent )
> Feb 12 09:47:21 capestor1 kernel: drbd0: Writing meta data super  
> block now.
>
> Looks like it attached because when I try the command again it says it
> is already attached.
>
> I will post my configs if needed but I am trying to understand a few  
> things.
> What does the failure mean in this case and is the resource really  
> attached?
>
> I read that initially both machines will show the resource being
> inconsistent until one is specifically set to primary which occurs
> later in the tutorial.
>
> Thanks
>
> Doug
>
>
>
> -- 
> What profits a man if he gains the whole world yet loses his soul?
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems