Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I just discovered that if I run 'drbdadm adjust r0' on the primary a second time, after running it on the secondary, that fixes everything. Did I misunderstand, and perhaps the command needs to be run first on the secondary, and then on the primary last? On Fri, Sep 21, 2012 at 7:44 AM, Lonni J Friedman <netllama at gmail.com> wrote: > On Fri, Sep 21, 2012 at 4:34 AM, Felix Frank <ff at mpexnet.de> wrote: >> On 09/21/2012 01:30 PM, Felix Frank wrote: >>>> > I don't understand how this is incompatible. At least the >>>> > documentation doesn't make any mention of what would make this >>>> > incompatible. >>> We have yet to see the configuration of the peer node. >>> >>> Test wether both nodes have actually loaded the current configuration, >>> either using drbdsetup <minor> show or drbdadm adjust --noop. >> >> Just noticed - same goes for your data-integrity-alg question. Can we >> agree to let that other thread die? ;) > > Sure. Hopefully whatever is causing me issues with after-sb-0pri will > fix data-integrity-alg too. If not, I can beat that horse later.