[DRBD-user] inital setup question ... 0.7.0 plus linux 2.6.6

Ron OHara rono at sentuny.com.au
Thu Jul 22 13:55:23 CEST 2004

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


Ok ... that worked ... but when I added the second box I got this ... 
All seems to have continued, but I thought I'd better let you know.

Ron

Jul 22 12:03:45 vossdir1 kernel: e1000: eth1 NIC Link is Up 100 Mbps 
Full Duplex
Jul 22 12:51:24 vossdir1 kernel: drbd1: Handshake successful: DRBD 
Protocol version 74
Jul 22 12:51:24 vossdir1 kernel: drbd0: Handshake successful: DRBD 
Protocol version 74
Jul 22 12:51:24 vossdir1 kernel: drbd1: 
/usr/local/src/drbd-0.7.0/drbd/drbd_receiver.c:1414: bitmap already 
locked by /us
Jul 22 12:51:24 vossdir1 kernel: drbd0: 
/usr/local/src/drbd-0.7.0/drbd/drbd_receiver.c:1414: bitmap already 
locked by /us
Jul 22 12:51:24 vossdir1 kernel: Call Trace:
Jul 22 12:51:24 vossdir1 kernel: Call Trace: [<f8a4c105>]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a4c105>] 
__drbd_bm_lock+0x105/0x14d [drbd]
Jul 22 12:51:24 vossdir1 kernel: __drbd_bm_lock+0x105/0x14d [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a57e18>] receive_param+0x21e/0x71d 
[drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a55aad>]  [<f8a57e18>] 
drbd_recv_header+0x2b/0xe6 [drbd]
Jul 22 12:51:24 vossdir1 kernel: receive_param+0x21e/0x71d [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a57bfa>]  [<f8a55aad>] 
receive_param+0x0/0x71d [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a58ab5>] 
drbd_recv_header+0x2b/0xe6 [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a57bfa>] drbdd+0x59/0x13f [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a5958f>] receive_param+0x0/0x71d 
[drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a58ab5>] drbdd_init+0x6c/0x1b8 [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a5f235>] drbdd+0x59/0x13f [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a5958f>] 
drbd_thread_setup+0x79/0xff [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a5f1bc>] drbdd_init+0x6c/0x1b8 [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a5f235>] 
drbd_thread_setup+0x0/0xff [drbd]
Jul 22 12:51:24 vossdir1 kernel: drbd_thread_setup+0x79/0xff [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<f8a5f1bc>]  [<c0104271>] 
drbd_thread_setup+0x0/0xff [drbd]
Jul 22 12:51:24 vossdir1 kernel:  [<c0104271>] kernel_thread_helper+0x5/0xb
Jul 22 12:51:24 vossdir1 kernel:
Jul 22 12:51:24 vossdir1 kernel: kernel_thread_helper+0x5/0xb
Jul 22 12:51:24 vossdir1 kernel: drbd0: Connection established.
Jul 22 12:51:24 vossdir1 kernel:
Jul 22 12:51:24 vossdir1 kernel: drbd1: Connection established.
Jul 22 12:51:24 vossdir1 kernel: drbd0: Primary/Unknown --> 
Primary/Secondary
Jul 22 12:51:24 vossdir1 kernel: drbd1: Primary/Unknown --> 
Primary/Secondary
Jul 22 12:51:24 vossdir1 kernel: drbd0: Resync started as SyncSource 
(need to sync 4063232 KB [1015808 bits set]).
Jul 22 12:51:24 vossdir1 kernel: drbd1: Resync started as SyncSource 
(need to sync 4063232 KB [1015808 bits set]).

Lars Ellenberg wrote:

>/ 2004-07-21 16:47:16 +0000
>\ Ron OHara:
>  
>
>>Hi Lars,
>>
>>(drbd-0.7.0 and linux 2.6.6)
>>
>>A question about initial setup ... I want to have a process for creating 
>>a standalone 'Primary' DRBD disk (dont ask why :-[ )
>>
>>So I build the first box of the cluster ... there is no data ... I just 
>>want to initialise a file system and be able to force this box to be the 
>>'primary'.
>>
>>then:
>>
>>drbdadm up all
>>
>>drbdadm primary all
>>
>>and this complains because it is in WFConnection, Secodary/Unknown  : 
>>Invalid
>>This is pretty much the expected state .. and I can force it to 
>>Standalone, but it still wont let me force it to Primary/Uknown so that 
>>I can mount the disk R/W and make a file system on it.
>>
>>Any ideas??
>>    
>>
>
>intentional behavior.
>drbadm primary all should says something like
>"Local replica is inconsistent (--do-what-I-say ?)"
>
>so it already gives you that hint: it needs to be forced,
>and you need to give it that additional option.
>
>now, since it is not a drbdadm option, but a drbdsetup option,
>you'd need to use drbsetup...
>but drbdadm is able to pass options to drbdsetup:
>
>USAGE: drbdadm [OPTION...] [-- DRBDSETUP-OPTION...] COMMAND {all|RESOURCE...}
>
>so, what you actually want to do is
> drbdadm -- --do-what-I-say primary all
>but you should be sure that you really mean what you say!
>
>  
>
>>Ron
>>(PS: I'm deliberately building what starts life as a degraded cluster 
>>..with later upgrade possible without reconfiguration)
>>    
>>
>
>sounds reasonable...
>
>	Lars Ellenberg
>_______________________________________________
>drbd-user mailing list
>drbd-user at lists.linbit.com
>http://lists.linbit.com/mailman/listinfo/drbd-user
>  
>




More information about the drbd-user mailing list