I made a ~1T snapshot, but trying to copy the repository from another machine caused this after several hours (after importing about 260G of data):
LoadBlob(9f02880a10db561af97a6e1d69d3cc85936951fc6eb020c638f5422ea2268c27) returned error blob 9f02880a10db561af97a6e1d69d3cc85936951fc6eb020c638f5422ea2268c27 returned invalid hash
- the host machine is an anemic mips machine, not very reliable
- the snapshot took about a week to make
- the backup machine is remote and much more reliable
- the backup machine uses rest-server (append only)
% restic -v stats repository 390a6747 opened successfully, password is correct scanning... Stats in restore-size mode: Snapshots processed: 1 Total File Count: 157211 Total Size: 991.686 GiB
% restic -v check using temporary cache in /tmp/restic-check-cache-341950296 repository 390a6747 opened successfully, password is correct created new cache in /tmp/restic-check-cache-341950296 create exclusive lock for repository load indexes check all packs check snapshots, trees and blobs [0:07] 100.00% 1 / 1 snapshots no errors were found
% restic -v find --blob 9f02880a10db561af97a6e1d69d3cc85936951fc6eb020c638f5422ea2268c27 Found blob 9f02880a10db561af97a6e1d69d3cc85936951fc6eb020c638f5422ea2268c27 ... in file /cen/so/red.mp3 (tree f73fb24fa4f8c0885452a51c3d97912efe44fd8f72907eda446bcada4463a309) ... in snapshot cd60b511 (2021-08-29 00:57:08)
I did check the integrity of the file on the host machine (compared to another reference of that specific file I had backed up somewhere else) and it’s correct.
Trying to figure out what the data looks like on the repository to compare how it is altered, but:
% restic -v cat blob 9f02880a10db561af97a6e1d69d3cc85936951fc6eb020c638f5422ea2268c27 repository 390a6747 opened successfully, password is correct blob 9f02880a10db561af97a6e1d69d3cc85936951fc6eb020c638f5422ea2268c27 returned invalid hash github.com/restic/restic/internal/repository.(*Repository).LoadBlob github.com/restic/restic/internal/repository/repository.go:210 main.runCat github.com/restic/restic/cmd/restic/cmd_cat.go:172 main.glob..func4 github.com/restic/restic/cmd/restic/cmd_cat.go:27 github.com/spf13/cobra.(*Command).execute email@example.com/command.go:856 github.com/spf13/cobra.(*Command).ExecuteC firstname.lastname@example.org/command.go:974 github.com/spf13/cobra.(*Command).Execute email@example.com/command.go:902 main.main github.com/restic/restic/cmd/restic/main.go:98 runtime.main runtime/proc.go:225 runtime.goexit runtime/asm_amd64.s:1371
- Any chance I could force a dump of that blob anyway?
- Can I copy the repo while skipping that invalid blob (to see if there are more)
- What could be the cause of the such corruption?