Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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