Hi,
How would one get rid of this persisting error? Pruning did not do away with it.
error: node "file1", last"file1": nodes are not ordered or duplicate
Thanks much
warnod
Hi,
How would one get rid of this persisting error? Pruning did not do away with it.
error: node "file1", last"file1": nodes are not ordered or duplicate
Thanks much
warnod
I would say if you want help you post more details?
It appeared one day during backup and stayed ever since. I am unsure what caused it.
open repository
lock repository
using parent snapshot <>
load index files
start scan on <>
start backup on <>
scan finished in 16.758s: <>
error: node "file1", last"file1": nodes are not ordered or duplicate
Files: 0 new, 5 changed, <> unmodified
Dirs: 0 new, 5 changed, <> unmodified
Data Blobs: 5 new
Tree Blobs: 6 new
Added to the repository: 232.127 KiB (60.269 KiB stored)
processed <> files, <> GiB in 0:59
snapshot <> saved
What version of restic?
What repo destination?
What command?
You think people can see your screen?
This is a filesystem problem not a restic problem; the folder in question contains two files with the same name. Please run fsck / chkdsk to fix. In recent restic versions, this error has been downgraded to a warning so that the backup still completes. But either way please repair the filesystem.