In a functional classic 3 node set up what is the expected state of the secondary node that is the lower resource with regards the upper resource?

trk-kvm-01 (primary for both resource levels)

   root@trk-kvm-01:~/scripts# drbd-overview
   [...]
     12:convirt/0                Connected Primary/Secondary  
   UpToDate/UpToDate _convirt           vda virtio
   [...]
   120:convirt-U/0         ^^12 Connected Primary/Secondary  
   UpToDate/UpToDate

trk-kvm-02 (secondary lower resource)

   root@trk-kvm-02:~/scripts# drbd-overview
   [...]
     12:convirt/0                Connected    Secondary/Primary
   UpToDate/UpToDate _convirt           vda virtio
   [...]
   120:convirt-U/0         ^^12 Unconfigured . .

trk-kvm-03 (secondary on upper resource)

   root@trk-kvm-03:/media/scratch# drbd-overview
   [...]
   120:convirt-U/0  Connected Secondary/Primary UpToDate/UpToDate

I see nowhere to set this node's IP yet the docs say this resource file "must be distributed across all nodes in the cluster — in this case, three
nodes."  What is the point of the convirt-U res file on trk-kvm-02?


*Paul O'Rorke*




On 2018-02-07 07:52 AM, Paul O'Rorke wrote:

Oh my!!!!

2 weeks of missing that typo and frustration.  Thank you both Yannis and Peter.  Peter, I thought you were pointing out the answer to my question - which file is it failing to find.  I normally copy the .res file to ensure they are always identical, and it was correct on nodes 1 and 2....

I really appreciate the help guys, it all makes sense now.  I was worried that I had a serious misunderstanding in what I was doing.

    root@trk-kvm-01:~# cat /proc/drbd
    version: 8.4.5 (api:1/proto:86-101)
    srcversion: 4B3E2E2CD48CAE5280B5205

    [...]
    12: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
        ns:4764 nr:0 dw:10719324 dr:21194772 al:1676 bm:0 lo:0 pe:0
    ua:0 ap:0 ep:1 wo:f oos:0
    [...]
    120: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent A
    r-----
        ns:19642880 nr:0 dw:0 dr:19645043 al:0 bm:0 lo:0 pe:0 ua:0
    ap:0 ep:1 wo:f oos:32782648
        [======>.............] sync'ed: 37.5% (32012/51196)M
        finish: 0:12:39 speed: 43,136 (38,896) K/sec

and

    root@trk-kvm-03:/media/scratch# drbd-overview
    120:convirt-U/0  SyncTarget Secondary/Primary Inconsistent/UpToDate
        [=======>............] sync'ed: 44.8% (28312/51196)M

Makes me very happy!

*Paul O'Rorke*
*Tracker Software Products (Canada) Limited *
www.tracker-software.com <http://www.tracker-software.com/>
Tel: +1 (250) 324 1621
Fax: +1 (250) 324 1623

<http://www.tracker-software.com/>

Support:
http://www.tracker-software.com/support
Download latest Releases
http://www.tracker-software.com/downloads/




On 2018-02-07 04:22 AM, Yannis Milios wrote:
Did you fixed the typo that Peter mentioned on his last post ? That should be "internal" and not "inetrnal". Then must copy the resource file on all 3 nodes.
>> meta-disk       inetrnal;
After fixing that you should be able to create the metadata and initialize  the stacked device by:

On trk-kvm-01 (assuming that this is the primary node):
drbdadm create-md --stacked convirt-U

On trk-kvm-03:
drbdadm create-md convirt-U    #this will create the required metadata on the underlying device (i.e /dev/trk-kvm-03-vg/convirt). No need to transfer metadata manually from trk-kvm-01)

On trk-kvm-01:
drbdadm --stacked adjust convirt-U

On trk-kvm-03:
drbdadm adjust convirt-U

On trk-kvm-01:
drbdadm --stacked -- --overwrite-data-of-peer primary convirt-U
cat /proc/drbd



Y




_______________________________________________
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