Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DRBD: Users

Changing the name of a resource

 

 

DRBD users RSS feed   Index | Next | Previous | View Threaded


chirayithaj at gmail

May 23, 2012, 2:50 PM

Post #1 of 2 (585 views)
Permalink
Changing the name of a resource

All:

Wanted to change the name of the drbd resource to better reflect its
functional use.

In test, Tried changing the file and resource name on the secondary side,
adjusting and re-connecting. And other slightly different steps, to see
what can work.

The results are that when re-connecting after changing the file name - the
primary side seems to think that the device is out of sync and becomes the
sync source but the secondary side will have none of it and goes it
'WFConnection' state.

Find below the log extract when the secondary side is connected after the
resource is renamed. ( From the log it seems that it does become the sync
target and actually syncs, but does not like something).

Is there a known sequence of steps that can work in this case ? Need I
experiment any further ? What else can I try ?

-JA

block drbd0: conn( StandAlone -> Unconnected )
block drbd0: Starting receiver thread (from drbd0_worker [32028])
block drbd0: receiver (re)started
block drbd0: conn( Unconnected -> WFConnection )
block drbd0: Handshake successful: Agreed network protocol version 96
block drbd0: Peer authenticated using 16 bytes of 'md5' HMAC
block drbd0: conn( WFConnection -> WFReportParams )
block drbd0: Starting asender thread (from drbd0_receiver [14379])
block drbd0: data-integrity-alg: md5
block drbd0: drbd_sync_handshake:
block drbd0: self
A3DA23FAA568B544:0000000000000000:CC820BAF75D3008A:CC810BAF75D3008B bits:0
flags:0
block drbd0: peer
518B27BC03329A91:A3DB23FAA568B545:A3DA23FAA568B545:CC820BAF75D3008B
bits:721870 flags:0
block drbd0: Did not got last syncUUID packet, corrected:
block drbd0: peer
518B27BC03329A91:A3DA23FAA568B545:CC820BAF75D3008B:CC820BAF75D3008B
bits:721870 flags:0
block drbd0: uuid_compare()=-1 by rule 51
block drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT )
disk( UpToDate -> Outdated ) pdsk( DUnknown -> UpToDate )
block drbd0: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 239(1),
total 239; compression: 99.9%
block drbd0: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 239(1),
total 239; compression: 99.9%
block drbd0: conn( WFBitMapT -> WFSyncUUID )
block drbd0: updated sync uuid
A3DB23FAA568B544:0000000000000000:CC820BAF75D3008A:CC810BAF75D3008B
block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0
block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0
exit code 0 (0x0)
block drbd0: conn( WFSyncUUID -> SyncTarget ) disk( Outdated ->
Inconsistent )
block drbd0: Began resync as SyncTarget (will sync 2887480 KB [721870 bits
set]).
block drbd0: Resync done (total 9 sec; paused 0 sec; 320828 K/sec)
block drbd0: 100 % had equal check sums, eliminated: 2887480K; transferred
0K total 2887480K
block drbd0: updated UUIDs
518B27BC03329A90:0000000000000000:A3DB23FAA568B544:A3DA23FAA568B545
block drbd0: conn( SyncTarget -> Connected ) disk( Inconsistent -> UpToDate
)
block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0
block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0 exit
code 0 (0x0)
block drbd0: bitmap WRITE of 0 pages took 0 jiffies
block drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map.
block drbd0: peer( Primary -> Unknown ) conn( Connected -> TearDown ) pdsk(
UpToDate -> DUnknown )
block drbd0: asender terminated
block drbd0: Terminating asender thread
block drbd0: Connection closed
block drbd0: conn( TearDown -> Unconnected )
block drbd0: receiver terminated
block drbd0: Restarting receiver thread
block drbd0: receiver (re)started
block drbd0: conn( Unconnected -> WFConnection )
block drbd0: conn( WFConnection -> Disconnecting )
block drbd0: Discarding network configuration.
block drbd0: Connection closed
block drbd0: conn( Disconnecting -> StandAlone )
block drbd0: receiver terminated
block drbd0: Terminating receiver thread
block drbd0: conn( StandAlone -> Unconnected )
block drbd0: Starting receiver thread (from drbd0_worker [32028])
block drbd0: receiver (re)started
block drbd0: conn( Unconnected -> WFConnection )


ff at mpexnet

May 24, 2012, 11:58 PM

Post #2 of 2 (546 views)
Permalink
Re: Changing the name of a resource [In reply to]

Hi,

On 05/23/2012 11:50 PM, John Anthony wrote:
> All:
>
> Wanted to change the name of the drbd resource to better reflect its
> functional use.
>
> In test, Tried changing the file and resource name on the secondary
> side, adjusting and re-connecting. And other slightly different steps,
> to see what can work.
>
> The results are that when re-connecting after changing the file name -
> the primary side seems to think that the device is out of sync and
> becomes the sync source but the secondary side will have none of it and
> goes it 'WFConnection' state.
>
> Find below the log extract when the secondary side is connected after
> the resource is renamed. ( From the log it seems that it does become the
> sync target and actually syncs, but does not like something).
>
> Is there a known sequence of steps that can work in this case ? Need I
> experiment any further ? What else can I try ?

I don't see how this is being problematic in any way. Resource names
only matter to the userland side of things. You need not adjust anything
at all - just update the drbd configs on both nodes. Use
drbd-overview.pl to check that the nodes are happy.

Why your node tears down the connection, I'm not sure. Do the peer's
logs reveal anything else?

Cheers,
Felix
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

DRBD users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.