Should -fossils be default for `duplicacy check`?

[quiet.car6978]

In the IEEE paper and on the “Lock-free deduplication algorithm” explanation, it’s stated that:

A restore, list, or check procedure that reads existing backups can read the fossil if the original chunk cannot be found.

However, on the duplicacy check page, it states that

By default the check command does not find fossils. If the -fossils option is specified, it will find the fossil if the referenced chunk does not exist.

This implementation seems to imply that in rare cases, duplicacy check (without the -fossils option) will error even though the repository is sound because a chunk was marked as a fossil even though it’s still being referenced. Am I understanding this correctly?

[saspus]

Yep, that is my understanding too. Relevant past discussion:

Missing chunk, can't figure out why

Add the -fossils option to the check job and this kind of errors won’t happen again. Maybe -fossils should be the default?

[quiet.car6978]

Ah, thanks for confirming. Just making sure I was understanding the pseudocode in the IEEE paper correctly. I’ll make sure to always run with -fossils.