Hi, On Thu, Feb 28, 2008 at 08:36:33AM +0100, rupert wrote: > has no one some ideas to this matter?
This is a drbd related issue. You should be better off in a drbd forum. Thanks, Dejan > thx > > On Tue, Feb 26, 2008 at 12:10 PM, rupert <[EMAIL PROTECTED]> wrote: > > Hello, > > > > i set up a cluster with 2 drbdb devices and 2 VM on each server. > > When one server goes down the other should take over the part of down one. > > The drbd goes like this: > > a -> a > > b <- b > > > > the other machine are not drbdb devices, just some loopback VM which > > caryy no data, > > can they be in the config for heartbeat? > > > > in my haresources I have the following entries on both servers > > > > xen-A1.fra1.mailcluster drbddisk::drbd_backend xen::backend-A1 xen::MX1-A1 > > xen-B1.fra1.mailcluster drbddisk::drbd_backend_2 xen::backend-B1 > > xen::MX2-B1 > > > > in ha.cf on the first server I set ucast to > > ucast eth0 172.20.1.1 > > and > > ucast eth0 172.20.2.1 > > on the second server > > > > when i restart the ha deamon it powers down all the VMs and makes on > > the first server > > all the drbd device primary but they should be on the first server > > > > GIT-hash: b3fe2bdfd3b9f7c2f923186883eb9e2a0d3a5b1b build by > > [EMAIL PROTECTED], 2008-02-13 19:17:43 > > 0: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r--- > > ns:135995280 nr:0 dw:779680 dr:135790386 al:224 bm:8602 lo:0 pe:0 ua:0 > > ap:0 > > resync: used:0/31 hits:8442668 misses:8308 starving:0 dirty:0 > > changed:8308 > > act_log: used:0/257 hits:136296 misses:224 starving:0 dirty:0 > > changed:224 > > 1: cs:Connected st:Secondary/Primary ds:UpToDate/UpToDate C r--- > > ns:0 nr:663968 dw:663968 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 > > resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0 > > > > > > on my first start heartbeat told me that the drbddisk is active and it > > shouldnt be, > > but its the one that is on each server the main drbdisk, the other is > > the backup > > for failouts. > > > > Resource drbddisk::drbd_backend_2 is active, and s > > > > hould not be! > > 2008/02/26_07:42:58 CRITICAL: Non-idle resources can affect data integrity! > > 2008/02/26_07:42:58 info: If you don't know what this means, then get help! > > 2008/02/26_07:42:58 info: Read the docs and/or source to > > /usr/share/heartbeat/Re > > > > sourceManager for more details. > > CRITICAL: Resource drbddisk::drbd_backend_2 is active, and should not be! > > CRITICAL: Non-idle resources can affect data integrity! > > info: If you don't know what this means, then get help! > > info: Read the docs and/or the source to > > /usr/share/heartbeat/ResourceManager fo > > > > r more details. > > 2008/02/26_07:42:58 CRITICAL: Non-idle resources will affect resource > > takeback! > > 2008/02/26_07:42:58 CRITICAL: Non-idle resources may affect data integrity! > > > > > > thx for your help > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems -- Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
