## C2: forced key, client names another path
$ lc.sh forced other-path snapshots
ID        Time                 Host        Tags        Paths
--------------------------------------------------------------
d807418c  2026-10-03 11:20:19  livebox     app1        /d/tree
68885c41  2026-10-03 11:20:22  livebox     app1        /d/tree
--------------------------------------------------------------
2 snapshots
[rc=0]

## A5: crash a backup mid-run (docker kill -s KILL)
killing r436-live-3883038 at 11:31:14
locks after crash:
-rw-rw-r-- 1 u629488-sub4 1061 141 Oct  3 11:31 96a4f54c6477793c31050da87ad5e835bbbed2ce76549634a1ccf6cf5a065524
$ lc.sh forced spike-r436 backup /d/tree --host livebox --tag app1
using parent snapshot 68885c41

Files:           0 new,     0 changed,     4 unmodified
Dirs:            0 new,     1 changed,     2 unmodified
Added to the repository: 325 B (274 B stored)

processed 4 files, 585.948 KiB in 0:00
snapshot 8f720f1d saved
[rc=0]

$ lc.sh forced spike-r436 check
using temporary cache in /tmp/restic-check-cache-2564422886
create exclusive lock for repository
unable to create lock in backend: repository is already locked by PID 1 on 91671d11c1a8 by root (UID 0, GID 0)
lock was created at 2026-10-03 11:31:08 (14.102493775s ago)
storage ID 96a4f54c
the `unlock` command can be used to remove stale locks
[rc=1]

## plain unlock
$ lc.sh forced spike-r436 unlock
successfully removed locks
[rc=0]

locks:
-rw-rw-r-- 1 u629488-sub4 1061 141 Oct  3 11:31 96a4f54c6477793c31050da87ad5e835bbbed2ce76549634a1ccf6cf5a065524
## unlock --remove-all
$ lc.sh forced spike-r436 unlock --remove-all
successfully removed locks
[rc=0]

locks:
$ lc.sh forced spike-r436 check
using temporary cache in /tmp/restic-check-cache-3405178813
create exclusive lock for repository
load indexes
pack c67a24b49d4e41a91d6de9448cb7c72623b6eb12ee8a50b7f4db2e2dfb465480 contained in several indexes: {85027deb a5b0181c}
pack 92475c24d7b0495584f168c7a73e6f0e35c9c27881c2ecbb0e18695b889cfb7f contained in several indexes: {85027deb a5b0181c}
This is non-critical, you can run `restic rebuild-index' to correct this
check all packs
pack 9783961d590d0675569230cf7662548d03914af0eebe1d4b1eb6b5573dafb9a8: not referenced in any index
pack 5aa289972c6799f5a18c991f3f2c36a2ac8fcdeb41ed5b2708807a774bc730ae: not referenced in any index
pack f16746415ed296cc92e78df06859b3fd2c0ba3deb73a31c97e8ed301ee7c214a: not referenced in any index
pack 51690a831d4a96fbeed192e0ff0ce879d309994ccb044ead6a1f2096baeea610: not referenced in any index
pack 38026bf50bc4028ef383ea19fbdeff362a925d6ecd4be66a3c635b8796fe623e: not referenced in any index
5 additional files were found in the repo, which likely contain duplicate data.
This is non-critical, you can run `restic prune` to correct this.
check snapshots, trees and blobs
[0:00] 100.00%  3 / 3 snapshots

no errors were found
[rc=0]

