Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 08/22/2012 05:18 PM, Lars Ellenberg wrote: >> d-con ResourceData2: BAD! BarrierAck #422870 received, expected #422875! >> After those minutes the synchronization seemed to work fine, and the >> system is now up and running. >> >> I've read elsewhere that these messages might be "over-paranoid", > > No, they are not. > Not in this case, at least. Is there reason to doubt the data integrity on the secondary side now that the sync is over? Will we need to trigger a complete re-sync once the fix is installed? > Unfortunately I'm working on some more issues (one being in-kernel list > corruption) before tagging and pushing rc2. > > Should happen later today/tomorrow, though. Ok, just let us know when to "git pull"... Regards, Lutz Vieweg