[DRBD-user] In the init script, what exactly is drbdadm waiting for, exactly?

Maurice Volaski mvolaski at aecom.yu.edu
Fri Oct 19 19:06:27 CEST 2007

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


>
>there should at least also be the drbdadm / drbdsetup process
>that is "waiting for nothing"? and its "children"?
>

Sorry, executed after I said "yes". Now before "yes"

10584 pts/0    S+     0:00 /bin/bash /sbin/runscript.sh ./drbd start
10639 pts/0    S+     0:00 /bin/bash /sbin/runscript.sh ./drbd start
[drbd processes deleted]
10839 pts/0    S+     0:00 /sbin/drbdadm wait-con-int
10840 pts/0    S+     0:00 /sbin/drbdsetup /dev/drbd0 wait-connect 
--degr-wfc-timeout=120 --wfc-timeout=0
10842 pts/0    S+     0:00 /sbin/drbdsetup /dev/drbd2 wait-connect 
--degr-wfc-timeout=120 --wfc-timeout=0

So according to that, it is specifically waiting on drbd0 and drbd2. 
But in /proc/drbd on the primary, it says:

0: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
2: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---


>  >
>  > >is there anything "unusual" in the kernel log?
>>
>
>
>not yet Connected

Sorry again, that was also the wrong section of the log. In a correct 
log on the secondary, they are connected:
Oct 19 12:52:12 [kernel] [234013.914593] drbd0: conn( SyncTarget -> 
Connected ) disk( Inconsistent -> UpToDate )
Oct 19 12:52:12 [kernel] [234013.966991] drbd2: conn( SyncTarget -> 
Connected ) disk( Inconsistent -> UpToDate )

I ran it again and again it was these same two that drbdsetup thinks 
are not connected despite the contrary evidence in /proc/drbd and the 
log.
-- 

Maurice Volaski, mvolaski at aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University



More information about the drbd-user mailing list