Little bit about locks

Getting Help
1

Hello,

I’m rather new to Restic but already have some backups and restore done - many people forget that backup without tested and confirmed working restore is useless. :smiley:
Setup:
I have about 10 all except one are Linux (one Win). hosts backing up to same repository located on NFS share of the NAS. As some hosts are remote - connected via VPN I have set up rest-server just not to use NFS over slow links, as we know NFS is not good at that. All hosts have latest (or one before) versions of restic - I do run self-update quite often.

Anyway about locks.
If there are stale locks - typically I do get warning from - restic forget (run daily) about lock. It does show date and time when created, but not host.
The question - Is there any way to see owner/host of the lock?

Another question - The directory /locks is not empty, it has one file:
694f82dd158788e5ea9d190847cc96afe79c983ce1fad399a8bccf4dc0118eda-tmp-2944677058
but when I run list locks none are shown and everything functions properly.
The file is 10 days old. What is this file and can I remove it?

Thanks! :wink:

2

Currently only with restic cat lock <id> .

Restic first uploads files into a temporary file, ensures that it is fully written and afterwards renames it to the final filename. This temporary file is probably left over due to some interrupted connection. You can just delete it, it’s not used anymore.