Hello,
I have the following repositories topology:
O (local) - repository contains snapshots with specific tag
L1 (restic S3) - repository contains snapshots from specific machine
L2 (restic S3) - repository contains snapshots from another similar machine
V (local) - repository which all the snapshots from repositories above are copied to
R1 - R3 (rclone) - repositories in different cloud storages which are snapshots from V are copied to
So here’s a kind of chain of snapshots.
Today I’ve noticed strange thing:
V contains 9950 snapshots
R1 - 9961
R2 - 9969
R3 - 10160
Results above are gathered with restic --no-cache ... snapshots
All the repositories are periodically checked with --read-data
and the last check was about a week ago without any issues.
copy from V to R1, R2, R3 is passed fine with no snapshots copied; R1 → V; R2 → V; R3 → V - the same (also with --no-cache
).
So how this could be even possible?
One more interesting thing found: check
subcommand reports it can’t access cache directory while other subcommands are creating it.
unable to create temporary directory for cache during check, disabling cache: stat /Volumes/Flash/Temp/Cache/restic/repo: no such file or directory