Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Note: This is a english re-post of "Versehentliches "drbdadm invalidate XXX" rückgängig machen ? " Hello list, I have a question regarding UNDO of the "drbdadm invalidate" command (prior to sync). We have a cluster of 2 machines, DRBD 8.2.6 and we had a split brain. The filesystem was active on both nodes - NodeA and NodeB. We did the following: - Thought NodeA had the latest data - drbdadm secondary on NodeB - drbdadm invalidate on NodeB now we found that NodeB had the latest data. We did not issue "connect" yet, so no data changed (only meta data) /proc/drbd: version: 8.2.6 (api:88/proto:86-88) ... 1: cs:StandAlone st:Secondary/Unknown ds:Inconsistent/DUnknown ra-- ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 oos:58562364 GI: 7A0A55CE55896BFE:0000000000000000:DB3807ED2AF2EC64:83495FFABA3A0737:0:0:0:0:0:0 How can I undo the "invalidate" command, so that I can change the resync direction afterwards ? The goal is to get back to the split brain situation, so hat I can issue "invalidate" on the other node (NodeA). I guess it's drbdmeta set-gi, however I tried ::::1:0:0:0:0:0 and ::::0:1:0:0:0:0, did not help. I also guess it's setting back the 00000000 above to a common parent GID (GID2 on the other node ?), but I would need some clarification :) P.s. This is a english re-post of "Versehentliches "drbdadm invalidate XXX" rückgängig machen ? " Thank you in advance, Robert _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user