[DRBD-user] linstor resource create fails

[Michał Szamocki]

Hello,

I need to propagate some resources to new_node. Therefore I run:
linstor resource create new_node resXXX --storage-pool drbdthinpool

and I get:
WARNING:
    Could not find suitable node to automatically create a tie breaking resource for 'resXXX'.
SUCCESS:
Description:
    New resource 'resXXX' on node 'new_node' registered.
Details:
    Resource 'resXXX' on node 'new_node' UUID is: c58ca809-dabe-42b1-b750-80a1fe340966
SUCCESS:
Description:
    Volume with number '0' on resource 'resXXX' on node 'new_node' successfully registered
Details:
    Volume UUID is: a9662450-e58a-4233-854f-88484527e561
SUCCESS:
    Added peer(s) 'new_node' to resource 'resXXX' on 'node1'
SUCCESS:
    Created resource 'resXXX' on 'new_node'
SUCCESS:
Description:
    Resource 'resXXX' on 'new_node' ready
Details:
    Node(s): 'new_node', Resource: 'resXXX'


but logical volume on new_node is almost empty (shows < 1 in Data%) and fs on drbd reports sevear error-s.

In logs I see:
Jan 23 07:11:02 node1 kernel: [75153.001066] drbd resXXX new_node: Starting sender thread (from drbdsetup [5269])
Jan 23 07:11:02 node1 kernel: [75153.004713] drbd resXXX/0 drbd1013: meta-data IO uses: blk-bio
Jan 23 07:11:02 node1 kernel: [75153.004997] drbd resXXX: Method to ensure write ordering: flush
Jan 23 07:11:02 node1 kernel: [75153.019568] drbd resXXX/0 drbd1013: resync bitmap: bits=13107462 words=1433635 pages=2801
Jan 23 07:11:02 node1 kernel: [75153.019572] drbd resXXX/0 drbd1013: size = 50 GB (52429848 KB)
Jan 23 07:11:02 node1 kernel: [75153.041065] drbd resXXX/0 drbd1013: recounting of set bits took additional 8ms
Jan 23 07:11:02 node1 kernel: [75153.042147] drbd resXXX new_node: conn( StandAlone -> Unconnected )
Jan 23 07:11:03 node1 kernel: [75153.567901] drbd resXXX new_node: Handshake to peer 0 successful: Agreed network protocol version 116
Jan 23 07:11:03 node1 kernel: [75153.568116] drbd resXXX new_node: Starting ack_recv thread (from drbd_r_resXXX [5281])
Jan 23 07:11:03 node1 kernel: [75153.620426] drbd resXXX/0 drbd1013 new_node: drbd_sync_handshake:
Jan 23 07:11:03 node1 kernel: [75153.620429] drbd resXXX/0 drbd1013 new_node: self 187FF37F746A3E3E:0000000000000000:0000000000000000:0000000000000000 bits:0 flags:20
Jan 23 07:11:03 node1 kernel: [75153.620431] drbd resXXX/0 drbd1013 new_node: peer 187FF37F746A3E3E:0000000000000000:0000000000000000:0000000000000000 bits:13107200 flags:20
Jan 23 07:11:03 node1 kernel: [75153.620432] drbd resXXX/0 drbd1013 new_node: uuid_compare()=no-sync by rule 40
Jan 23 07:11:03 node1 kernel: [75153.621778] drbd resXXX/0 drbd1013 new_node: pdsk( DUnknown -> UpToDate ) repl( Off -> Established )
Jan 23 07:11:32 node1 Satellite[32043]: 07:11:32.210 [MainWorkerPool-9] INFO  LINSTOR/Satellite - SYSTEM - Resource 'resXXX' updated for node 'node1'.
Jan 23 07:11:32 node1 Satellite[32043]: 07:11:32.210 [MainWorkerPool-9] INFO  LINSTOR/Satellite - SYSTEM - Resource 'resXXX' updated for node 'new_node'.

but there is no "Began resync as" and pdsk is immediately UpToDate.

What should I do to have resXXX properly propagated on new_node?

RB,
Michał Szamocki
Cirrus