lars.ellenberg at linbit
Sep 17, 2007, 1:43 AM
Post #2 of 2
(355 views)
Permalink
|
On Fri, Sep 14, 2007 at 06:08:36PM +0200, Stefan Lesicnik wrote:
>
> Hi all,
>
> Me again! Heh.
>
> Maybe im missing a concept here, but this isnt working as expected (for
> me anyways! :) )
>
>
> Ubuntu 7.04
there should be log files somewhere on that system.
have look for drbd and network related messages from the kernel
during the relevant time.
my guess is that there is some zero-conf-make-it-easy-for-laptop-users
"automagic" going on, which unconfigured the nic when you unplug the
cable. and sorry, if the ip drbd is supposed to bind to is not there,
it won't retry. but, that's a guess, only.
> Heartbeat (from gutsy backport - 2.1.2 (i wanted dopd and
> drbd-peer-outdater)
> drbd 8.0.6 kernel module and userspace tools
>
> Node1 and Node2. drbd working in Primary / Secondary all mounted
> working fine.
>
> I pull the network cable from Node 1. Node 2 detects, migrates
> resources, mounts drive, becomes primary. yay!
and it should not, because you should have configured more than one
communication channel for heartbeat, so it would know that the other
node is still alive, but only this one network link is down.
> I plug the network cable back in, i expect heartbeat to return to Node
> 1, and it mostly does, just the disk state is as follows
>
>
> >From Node 1
>
> root[at]lsd-server:/var/log# cat /proc/drbd
> version: 8.0.6 (api:86/proto:86)
> SVN Revision: 3048 build by root[at]lsd-server, 2007-09-14 17:27:39
> 0: cs:StandAlone st:Primary/Unknown ds:UpToDate/Outdated r---
> ns:20 nr:0 dw:112 dr:1772 al:2 bm:2 lo:0 pe:0 ua:0 ap:0
> resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
> act_log: used:0/257 hits:26 misses:2 starving:0 dirty:0 changed:2
>
>
> and on Node 2
>
> root[at]candyflip:/var/log# cat /proc/drbd
> version: 8.0.6 (api:86/proto:86)
> SVN Revision: 3048 build by root[at]candyflip, 2007-09-13 12:17:47
> 0: cs:StandAlone st:Secondary/Unknown ds:UpToDate/DUnknown r---
> ns:1003960 nr:20 dw:116 dr:1004880 al:0 bm:64 lo:0 pe:0 ua:0 ap:0
> resync: used:0/31 hits:62686 misses:62 starving:0 dirty:0 changed:62
> act_log: used:0/257 hits:24 misses:0 starving:0 dirty:0 changed:0
>
>
> It has returned back to Node 1 correctly though (mounted fs etc)
>
>
> What exactly should I be doing now in this situation and how can i get
> the drbd talking again. I may be mistaken, but in my playing, the only
> way to fix it was to restart drbd.
>
> both sides report
>
> root[at]candyflip:/var/log# drbdadm cstate r0
> StandAlone
>
> thanks a lot :)
>
> stefan
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user[at]lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
--
: Lars Ellenberg http://www.linbit.com :
: DRBD/HA support and consulting sales at linbit.com :
: LINBIT Information Technologies GmbH Tel +43-1-8178292-0 :
: Vivenotgasse 48, A-1120 Vienna/Europe Fax +43-1-8178292-82 :
__
please use the "List-Reply" function of your email client.
_______________________________________________
drbd-user mailing list
drbd-user[at]lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
|
