Same storage, different check results from different computers

I have a bit of a strange issue. When I check my storage from one computer, the check successfully completes with no errors. However, when I check the same storage from another computer, it shows that I’m missing chunks. When I look for the chunks reported missing, I cannot find them, so they do seem to be missing. However, checking storage for the same backup and same revision reports as complete from another computer.

Selected log results below:

Check job 1 (running from another computer that is backing up to an server that has the storage drives in it)

Although the storage has a different name here than in check job 2, it is the same storage mapped to the same root directory (but mounted remotely)

This shows a number of missing chunks in different backups. I’ve just included a sample of the missing chunks from one job below.

Options: [-log check -storage LocalMain-DrivePool -a -tabular]
2024-02-22 20:18:43.583 INFO STORAGE_SET Storage set to sftp://root@192.168.2.234:22//mnt/user/backup/duplicacy/duplicacy
2024-02-22 20:18:43.769 INFO SNAPSHOT_CHECK Listing all chunks
2024-02-22 20:22:50.410 INFO SNAPSHOT_CHECK 26 snapshots and 251 revisions
2024-02-22 20:22:50.423 INFO SNAPSHOT_CHECK Total chunk size is 1375G in 328628 chunks
...
Skipping many lines of logs to show the snapshot ID below that is reported as complete from the other computer
...
2024-02-22 20:22:53.671 WARN SNAPSHOT_VALIDATE Chunk a35eef0aca48583797ac8f60a42fc92c19409e289b9eb8b54c4908d1f5b9b146 referenced by snapshot iMac-5k at revision 921 does not exist
2024-02-22 20:22:53.680 WARN SNAPSHOT_VALIDATE Chunk 08b8920d58dc2f4f55947c2dcb767889f9eb2d2d01f1c1f36c2c7e7beab1e4cd referenced by snapshot iMac-5k at revision 921 does not exist
2024-02-22 20:22:53.689 WARN SNAPSHOT_VALIDATE Chunk b1fba56b802cc9731ad1b10505b2158c025e1d12bbc8204ffef374bc06a9d5c1 referenced by snapshot iMac-5k at revision 921 does not exist
2024-02-22 20:22:53.695 WARN SNAPSHOT_VALIDATE Chunk a4f4dea3899a0a96267e09b262420021c5b9e087baab2d092faa386e563b9365 referenced by snapshot iMac-5k at revision 921 does not exist
These lines repeat for several more missing chunks in several different backup jobs...

Check job 2 (running from Unraid server where data is stored locally):

Running check command from /cache/localhost/all
Options: [-log check -storage unRAID -stats -tabular -a -tabular]
2024-02-22 20:15:46.201 INFO STORAGE_SET Storage set to /backuproot/backup/duplicacy/duplicacy
2024-02-22 20:15:46.265 INFO SNAPSHOT_CHECK Listing all chunks
2024-02-22 20:19:58.378 INFO SNAPSHOT_CHECK 26 snapshots and 251 revisions
2024-02-22 20:19:58.386 INFO SNAPSHOT_CHECK Total chunk size is 1375G in 328628 chunks
-----
Skipping down to the point in the logs where the revision with missing chunks is reported complete
-----
2024-02-22 20:20:04.140 INFO SNAPSHOT_CHECK All chunks referenced by snapshot iMac-5k at revision 921 exist

This revision 921 for the snapshot in question shows as complete here, but with numerous missing chunks from the other computer.

What would cause this, and do you have any recommendations for how I can get things in sync so I get the same results from both computers?

Thank you.

Duplicacy caches chunks locally.

I’m wondering if there is some corner case with check whether it checks the local cache but not the remote?

Try renaming the cache folder (under .duplicacy) and see if it starts failig on the first machine

Another possibility is perhaps maybe some chunks got uploaded by a different user and are not readable/accessible by the user doing the check?

1 Like

Thanks for the quick reply @saspus. After renaming the cache folder, the check completed successfully. Thanks for the advice!

1 Like

@gchen — this looks like a bug.

I thought duplicacy only uses cached chunk if the one exists on the remote?

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.