[DRBD-user] One resource conected, one not?

Lars Ellenberg lars.ellenberg at linbit.com
Wed Apr 9 12:03:53 CEST 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Tue, Apr 08, 2008 at 03:56:39PM -0400, Rob Morin wrote:
> Rob Morin wrote:
>> Hello all , i was trying to implement into production last night drbd  
>> with heartbeat, i got it working fine in a dev environment, but last  
>> night try into production did nto work at all, i am not sure why at  
>> the moment, but meanwhile, before i try putting into production last  
>> night a few months ago i installed drbd and had that replicating  
>> flawlessly... howerver after last nights trial and error i know end up  
>> with this...
>>
>> joe:/etc/init.d# cat /proc/drbd
>> version: 8.0.4 (api:86/proto:86)
>> SVN Revision: 2947 build by root at joe, 2008-02-15 12:14:56
>> 0: cs:StandAlone st:Primary/Unknown ds:UpToDate/DUnknown   r---
>>    ns:0 nr:0 dw:827600 dr:3253811 al:1469 bm:1869 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:205431 misses:1566 starving:0 dirty:97  
>> changed:1469
>> 1: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
>>    ns:5959720 nr:0 dw:5959720 dr:2872578 al:12120 bm:231 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:1477810 misses:12398 starving:0  
>> dirty:278 changed:12120
>>
>> What would cause one resource to be connected and another not?

your kernel logs should tell you.

>> Any ideas?
>> I am using drbd 8 on Debian Etch

drbd8 (8.0.4-0)     27 Jun 2007 <=- you are here.
drbd8 (8.0.5-0)      3 Aug 2007
drbd8 (8.0.6-0)      3 Sep 2007
drbd8 (8.0.7-0)      2 Nov 2007
drbd8 (8.0.8-0)      6 Dec 2007
drbd8 (8.0.11-0)    12 Feb 2008
drbd8 (8.0.12rc1-0)  8 Apr 2008 <=- we are there

> Any ideas? i tried the split brain solution and still nothing i did a  

look into the kernel log.

> disconnect all and then connect all, and nothing....

> p.s. since i am using a second nic for the replication(eth0) in this  
> case, the broadcast of heartbeat should be on eth0 too right? not the  
> public/real IP?

typically heartbeat should use _all_ available communication channels.
as many as possible.

-- 
: 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 don't Cc me, but send to list -- I'm subscribed



More information about the drbd-user mailing list