Figured it out.  It seems it is a DBus issue.  It was caused by a bug.  If you 
have your volumes set to primary you configuration will not work.  Set to 
secondary and set auto-promote.


> On May 19, 2016, at 9:37 PM, Jason Romo <[email protected]> wrote:
> 
> Does anyone have an ideas why Primary and secondary are not syncing?  They 
> are connected, but not resources.
> 
> Thanks,
> Jason
>> On May 17, 2016, at 8:34 PM, Jason Romo <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hello all,
>> I configured these 3 servers two for storage one a controller.  They worked 
>> fine here.  Move them to the data center and now can’t get the Secondary to 
>> sync.  If I push VM to the secondary it works.  But takes a long time 
>> because the secondary has no LV and has to create the disk and pull all 
>> data. Before I move it it was keep them both in sync and I could move 
>> without an issue.  
>> 
>> How do I fix this?  Do I need to assign the resource to the secondary?  it 
>> worked before not hot sure what I am missing. Yes I know ve3 is still 
>> connecting, changing the 10Gbe interface on that box right now, but it is 
>> not for storage anyway.
>> 
>> Thanks,
>> Jason
>> 
>> VE1 Primary:
>> drbdadm status
>> .drbdctrl role:Primary
>>   volume:0 disk:UpToDate
>>   volume:1 disk:UpToDate
>>   ve2 role:Secondary
>>     volume:0 peer-disk:UpToDate
>>     volume:1 peer-disk:UpToDate
>>  
>> vm-102-disk-1 role:Primary
>>   disk:UpToDate
>>   ve2 role:Secondary
>>     peer-disk:Diskless
>> 
>> vm-103-disk-1 role:Primary
>>   disk:UpToDate
>> 
>> vm-105-disk-1 role:Primary
>>   disk:UpToDate
>> 
>> vm-106-disk-1 role:Primary
>>   disk:UpToDate
>>   ve2 connection:Connecting
>> 
>> vm-107-disk-1 role:Primary
>>   disk:UpToDate
>> 
>> vm-110-disk-1 role:Primary
>>   disk:UpToDate
>> 
>> vm-120-disk-1 role:Primary
>>   disk:UpToDate
>>   ve2 connection:Connecting
>> 
>> 
>> 
>> VE2 secondary:
>> drbdadm status
>> .drbdctrl role:Secondary
>>   volume:0 disk:UpToDate
>>   volume:1 disk:UpToDate
>>   ve1 role:Primary
>>     volume:0 peer-disk:UpToDate
>>     volume:1 peer-disk:UpToDate
>> 
>> vm-102-disk-1 role:Secondary
>>   disk:Diskless
>>   ve1 role:Primary
>>     peer-disk:UpToDate
>> 
>> 
>> VE1 Primary:
>> drbd-overview
>>   0:.drbdctrl/0      Conn(ve2,ve1)/C'ng(ve3) Prim(ve1)/Seco(ve2)/Unkn(ve3) 
>> UpTo(ve1)/UpTo(ve2)/DUnk(ve3) 
>>   1:.drbdctrl/1      Conn(ve2,ve1)/C'ng(ve3) Prim(ve1)/Seco(ve2)/Unkn(ve3) 
>> UpTo(ve1)/UpTo(ve2)/DUnk(ve3) 
>> 100:vm-102-disk-1/0  Connected(2*)           Primar/Second                 
>> UpToDa/Diskle                
>> 101:vm-107-disk-1/0  Connected(1*)           Primary(1*)                   
>> UpToDate(1*)                 
>> 102:vm-106-disk-1/0  Connec/C'ting           Primar/Unknow                 
>> UpToDa/DUnkno                
>> 103:vm-110-disk-1/0  Connected(1*)           Primary(1*)                   
>> UpToDate(1*)                 
>> 104:vm-105-disk-1/0  Connected(1*)           Primary(1*)                   
>> UpToDate(1*)                 
>> 105:vm-103-disk-1/0  Connected(1*)           Primary(1*)                   
>> UpToDate(1*)                 
>> 106:vm-120-disk-1/0  Connec/C'ting           Primar/Unknow                 
>> UpToDa/DUnkno    
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> drbd-user mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.linbit.com/mailman/listinfo/drbd-user
> 
> _______________________________________________
> drbd-user mailing list
> [email protected]
> http://lists.linbit.com/mailman/listinfo/drbd-user

_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to