On Fri, Dec 12, 2008 at 11:32:15AM +0100, Tobias Appel wrote: > Hi, > > I have a weird problem with DRBD. > I've created my Master / Slave Resource for the DRBD Service and got > another resource group which will mount the filesystem. I'm also using > the correct constraints and so on. > If I have a failover Heartbeat will set the active node to primary and > then mount the filesystem. So far so good. > But DRBD is not syncing between those nodes. > The active node says: 0: cs:WFConnection st:Primary/Unknown > ds:UpToDate/DUnknown C r--- > > Whereas the passive node tells me: 0: cs:StandAlone > st:Secondary/Unknown ds:UpToDate/DUnknown r--- > > > I haven't touched the DRBD config file but before I added it to > Heartbeat I tested it manually and it worked and was syncing just fine. > > I don't even know where to start to look for an error. drbd.conf ? The > configuration of my constraints or the m/s resource? > > Any advice is much appreciated!
closely drbd related questions probably go best to the drbd-users list, though multi-state (master slave) resource agent questions best go here. do NOT try to "fake" the host name with the DRBD m/s OCF RA. will not work. grep in the kernel logs for the reason why drbd was going to StandAlone. my best guess is that the "before resync target handler" returned some bad exit code because you faked the hostname in the OCF RA parameters. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
