The call to store pre-restore dbhashes in the movePrimary magic restore test stores the hashes from the data on the secondary node. Since we're able to acknowledge a write before it is applied, it's possible movePrimary completes and returns before the document deletion in the config.collection_critical_sections collection occurs. This results in the dbhash being mismatched when we compare it to the post-restore hash, which expects an empty critical section document.