Rebuilding a destination file system as part of a resync operation

A computing device, comprising:

• a memory comprising machine executable code;
• and
• a processor coupled to the memory, the processor configured to execute the machine executable code to cause the machine to perform operations comprising:
• receiving, by a destination storage node as part of a resync operation, changed blocks from a source storage node in response to the destination storage node recovering from a failure;
• receiving, by the destination storage node from the source storage node during the resync operation, inode information of clone files and parent information of parent files;
• logging the inode information and the parent information into a destination metafile as logged information;
• and
• replaying the logged information from the destination metafile to create reconstructed clone files as part of reconstructing a destination file system at the destination storage node, wherein the replaying includes creating a reconstructed clone file utilizing a set of shared blocks received from the source storage node.

A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to perform operations comprising:

• receiving, by a destination storage node as part of a resync operation, changed blocks from a source storage node in response to the destination storage node recovering from a failure;
• receiving, by the destination storage node from the source storage node during the resync operation, inode information of clone files and parent information of parent files;
• logging the inode information and the parent information into a destination metafile as logged information;
• and
• replaying the logged information from the destination metafile to create reconstructed clone files as part of reconstructing a destination file system at the destination storage node, wherein the replaying comprises:
• reconstructing a clone file as a reconstructed clone file and a parent file as a reconstructed parent file at the destination storage node;
• and
• utilizing the parent file information to merge a first internal representation of the reconstructed clone file with a second internal representation of the reconstructed parent file.