Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 2017-09-25 07:28 AM, Lars Ellenberg wrote:
> On Sat, Sep 23, 2017 at 11:32:42PM -0400, Digimer wrote:
>> I tried updating an 8.3.19 DRBD install (on EL6.9), and when I tried to
>
> 8.3.16 is the latest I know... typo I assume.
Yup, typo. Was late...
>> connect the updated node to the older node, I got this error:
>>
>> ==[ old node ]==
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd0: Handshake successful: Agreed network protocol version 97
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd0: conn( WFConnection -> WFReportParams )
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd0: Starting asender thread (from drbd0_receiver [12308])
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd0: incompatible after-sb-0pri settings
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd0: conn( WFReportParams -> Disconnecting )
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd0: error receiving ReportProtocol, l: 25!
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd1: Handshake successful: Agreed network protocol version 97
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd1: conn( WFConnection -> WFReportParams )
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd1: Starting asender thread (from drbd1_receiver [7326])
>> Sep 23 23:13:47 an-a02n02 kernel: block drbd1: incompatible after-sb-0pri settings
>
> You have incompatible "after-sb-0pri" settings.
I saw that, but the docs said the config was backwards compatible and
the after-sb-0pri was left as default.
>> ==[ updated node ]==
>
>> Sep 23 23:13:47 an-a02n01 kernel: drbd r0: incompatible after-sb-0pri settings
>
>> ====================
>>
>> The config is (from 'drbdadm dump'):
>>
>> ====
>> # /etc/drbd.conf
>> common {
>> protocol C;
>> net {
>> allow-two-primaries;
>> after-sb-0pri discard-zero-changes;
>
> So it claims it does not like this setting,
> respectively that the handshake expected that setting
> to be identical on both nodes, but it was not.
Isn't this the default back in 8.3 days? I don't recall ever changing it...
>> ====
>>
>> I downgraded the node back to 8.3.16 and tried to reconnect;
>>
>> ====
>> Starting DRBD resources: [
>> r0
>> no suitable meta data found :(
>> Command '/sbin/drbdmeta 0 v08 /dev/sda5 internal check-resize'
>> terminated with exit code 255
>> drbdadm check-resize r0: exited with code 255
>> d(r0) 0: Failure: (119) No valid meta-data signature found.
>
> DRBD 8.4 and 8.3 have slightly different meta data "magics".
> If you want to step back, you need to "convert" the 8.4
> back to the 8.3 magic, using the 8.4 compatible drbdmeta tool,
> because, well, unsurprisingly the 8.3 drbdmeta tool does not know
> the 8.4 magics.
>
> So if you intend to downgrade to 8.3 from 8.4,
> while you still have the 8.4 tools installed,
> do: "drbdadm down all; drbdadm apply-al all"
> Only then downgrade.
Noted for the future. In this case, I recreated the MD and did a full
resync.
--
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould