I was running an restore and I got those errors:
admin@NAS:/volume1/homes/tim$ ./restic -r /volume1/bak/restic-repository/ restore --verify --target /volume1/homes/peter/restore 19b421b0
enter password for repository:
repository 4788ce08 opened (version 2, compression level auto)
[1:08] 100.00% 3210 / 3210 index files loaded
restoring snapshot 19b421b0 of [/volume1] at 2024-02-11 20:02:02.269169257 +0100 CET by tim@NAS to /volume1/homes/peter/restore/
Remove(<lock/58fea5d6c7>) failed: chmod /volume1/bak/restic-repository/locks/58fea5d6c70008f36fe0ae35979daad0bc3861f363a5dfa5f2d6ee0c173a4d5d: no such file or directory
unable to refresh lock: chmod /volume1/bak/restic-repository/locks/58fea5d6c70008f36fe0ae35979daad0bc3861f363a5dfa5f2d6ee0c173a4d5d: no such file or directory
Remove(<lock/ce7a6cffd4>) failed: chmod /volume1/bak/restic-repository/locks/ce7a6cffd40b4afd8f814706111a2112e2ba2e7b9bb9f746a8cbd77e336ebe09: no such file or directory
unable to refresh lock: chmod /volume1/bak/restic-repository/locks/ce7a6cffd40b4afd8f814706111a2112e2ba2e7b9bb9f746a8cbd77e336ebe09: no such file or directory
Summary: Restored 91848 / 91846 files/dirs (239.907 GiB / 239.907 GiB) in 4:54:48
verifying files in /volume1/homes/peter/restore/
Did those locking errors prevented a complete and clean restore?