jxsl13 / backupfs Goto Github PK

I would like to merge two backup file systems to one another where one is merged into the other.
The appended backupfs ceases to exist, meaning, the backup is merged into the initial backupfs and deleted afterwards.

In case that an object

• did not exist in the first place
• was created
• and then removed again

This will create a nil FileInfo in the internal file map.

That entry may be deleted in the internal map, as it is the state that the filesystem currently has.
Reduces lstat and other operations.

rollback of symbolic links does not remove new symbolic links that were previously not there

Untar-ing an archive with symbolic links seems to create those properly but not remove them upon rollback.

the internally used file tracking logic may be wrapped in an own interface that can be a wrapper for the base fulesystem.

this way the internal tracking logic may be swapped with another implementation which allows for a different serialization implementation.

TrackFs or TraceFs

Potential references:
ipfs/kubo#4956

In specific edge cases it is possible that the underlying function calls return an error.

For example when creating a symlink and another file or symlink already exists, we do backup the file but the underlying symlink function does return an error thus we should remove the backup and potentially rollback the function call.