Can someone point me in the right direction to unpick this issue?
Thanks…
Setup…
~⸾ cat /etc/issue
Ubuntu 22.04.5 LTS \n \l
~⸾ incus version
Client version: 6.13
Server version: 6.13
~⸾ incus info jitsi
Name: jitsi
Description:
Status: STOPPED
Type: container
Architecture: x86_64
Created: 2024/10/05 22:18 BST
Last Used: 2025/06/27 13:07 BST
Now we successfully copy the container to the backup server, followed by a successful snapshot creation…
~⸾ incus copy jitsi backup:jitsi --mode=push
~⸾ incus snapshot create jisti 2025-06-26-daily
Container…
Name: jitsi
Description:
Status: STOPPED
Type: container
Architecture: x86_64
Created: 2024/10/05 22:18 BST
Last Used: 2025/06/27 13:07 BST
Snapshots:
+------------------+----------------------+------------+----------+
| NAME | TAKEN AT | EXPIRES AT | STATEFUL |
+------------------+----------------------+------------+----------+
| 2025-06-26-daily | 2025/06/27 15:23 BST | | NO |
+------------------+----------------------+------------+----------+
Now we refresh without the snapshot which is successful…
~⸾ incus copy jitsi backup:jitsi --mode=push --refresh --instance-only
Now we attempt to refresh with the snapshot…
~⸾ incus copy jitsi backup:jitsi --mode=push --refresh
Error: Failed instance migration: Failed migration on source: Failed to run: btrfs property set -f -ts /var/lib/incus/storage-pools/srv/containers-snapshots/jitsi/2025-06-23-daily ro true: exit status 1 (ERROR: Could not open: No such file or directory)
It appears to be trying to access a snapshot which doesn’t exist on this container?
There is no 2025-06-23-daily, the snapshot was 2025-06-26-daily?
~⸾ ll /srv/incus/containers-snapshots/jitsi/
total 0
drwx------ 1 root root 32 Jun 27 15:23 ./
drwx--x--x 1 root root 74 Jun 27 15:23 ../
d--x------ 1 root root 78 Jun 27 08:34 2025-06-26-daily/
~⸾ btrfs subvol list /srv | grep jitsi
ID 26577 gen 4309629 top level 26521 path incus/containers/jitsi
ID 26594 gen 4309603 top level 26521 path incus/containers-snapshots/jitsi/2025-06-26-daily
I think maybe theres an issue in the SQL database?
I used to fix things like this by looking at the storage volumes table.