Ok I managed to remove the logical volumes and drbdmanage uninit  Then 
remove-node on primary.  Then tried to add-node again.  I now get this:
root@ve1:# drbdmanage add-node ve2 192.168.202.2
Operation completed successfully
Operation completed successfully

Executing join command using ssh.
IMPORTANT: The output you see comes from ve2
IMPORTANT: Your input is executed on ve2
You are going to join an existing drbdmanage cluster.
CAUTION! Note that:
  * Any previous drbdmanage cluster information may be removed
  * Any remaining resources managed by a previous drbdmanage installation
    that still exist on this system will no longer be managed by drbdmanage

Confirm:

  yes/no: yes
  Failed to find logical volume "drbdpool/.drbdctrl_0"
  Failed to find logical volume "drbdpool/.drbdctrl_1"
  Logical volume ".drbdctrl_0" created.
  Logical volume ".drbdctrl_1" created.
You want me to create a v09 style flexible-size internal meta data block.
There appears to be a v09 flexible-size internal meta data block
already in place on /dev/drbdpool/.drbdctrl_0 at byte offset 4190208

Do you really want to overwrite the existing meta-data?
*** confirmation forced via --force option ***

Do you want to proceed?
*** confirmation forced via --force option ***
NOT initializing bitmap
md_offset 4190208
al_offset 4157440
bm_offset 4153344

Found some data

 ==> This might destroy existing data! <==
initializing activity log
Writing meta data...
New drbd meta data block successfully created.
You want me to create a v09 style flexible-size internal meta data block.
There appears to be a v09 flexible-size internal meta data block
already in place on /dev/drbdpool/.drbdctrl_1 at byte offset 4190208

Do you really want to overwrite the existing meta-data?
*** confirmation forced via --force option ***

Do you want to proceed?
*** confirmation forced via --force option ***
NOT initializing bitmap
md_offset 4190208
al_offset 4157440
bm_offset 4153344
Found some data

 ==> This might destroy existing data! <==
initializing activity log
Writing meta data...
New drbd meta data block successfully created.
Error: Operation not allowed on satellite node


I can’t find anything on how to resolve this.  Any Ideas?  I can’t even add the 
—force with add-node.  seems that is not a valid options with that command.

Jason






> On May 12, 2016, at 6:51 PM, Jason Romo <ja...@securityarsenal.com> wrote:
> 
> Hello all new to the group,
> 
> DRBD9 was working just fine.  I moved servers to the datacenter after a few 
> weeks of testing.  I loaded two VMs and I thought they had synced.  I guess 
> they didn’t.  The primary is fine.  I have since added new images to the 
> primary but not being passed. I guess due to the error on the two resources 
> in diskless state. The secondary in this state:
> 
> 
> VE1 is primary
> VE2 is secondary
> 
> VE1> says connecting for all resources, but volumes are UpToDate.  Guess it 
> is due to the errors on the secondary.
> 
> VE2> 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
> 
> vm-107-disk-1 role:Secondary
>   disk:Diskless
> 
> 
> 
> I tried to disconnect and adjust, disconnect and —force down, up.  I just get 
> this error:
> 
> VE2: adjust
> open(/dev/drbdpool/vm-102-disk-1_00) failed: No such file or directory
> Command 'drbdmeta 100 v09 /dev/drbdpool/vm-102-disk-1_00 internal apply-al' 
> terminated with exit code 20
> open(/dev/drbdpool/vm-107-disk-1_00) failed: No such file or directory
> Command 'drbdmeta 101 v09 /dev/drbdpool/vm-107-disk-1_00 internal apply-al' 
> terminated with exit code 20
> 
> 
> VE2: connect all
> .drbdctrl: Failure: (125) Device has a net-config (use disconnect first)
> Command 'drbdsetup connect .drbdctrl 0' terminated with exit code 10
> vm-102-disk-1: Failure: (162) Invalid configuration request
> additional info from kernel:
> unknown connection
> Command 'drbdsetup connect vm-102-disk-1 1' terminated with exit code 10
> vm-107-disk-1: Failure: (162) Invalid configuration request
> additional info from kernel:
> unknown connection
> Command 'drbdsetup connect vm-107-disk-1 1' terminated with exit code 10
> 
> I don’t have any resources on the secondary.  So If there is a way to just 
> have it drop it all and pull from primary again that works.  Or how can I 
> repair this state so I can get the secondary to pull the other images.  
> 
> Thanks again for any advice,
> Jason
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> drbd-user mailing list
> drbd-user@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user

_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to