Hi there,
Not sure if it’s a bug or just as designed, but after moving/copying a container residing on a btrfs pool to another storage pool or host (on btrfs too) , it leaves the received_uud set, which is wrong according btrfs itself:
sudo btrfs sub show /storage/root/incus/containers/wifi
WARNING: the subvolume is read-write and has received_uuid set,
don't use it for incremental send. Please see section
'SUBVOLUME FLAGS' in manual page btrfs-subvolume for
further information.
incus/containers/wifi
Name: wifi
UUID: 77a79dc7-ae0a-b64a-bcd0-3c05c4493b25
Parent UUID: -
Received UUID: 280a133d-ff1a-1b4f-9b9a-8651a912e523
Creation time: 2026-06-24 13:35:32 +0200
Subvolume ID: 4174
Generation: 1099881
Gen at creation: 1099875
Parent ID: 4006
Top level ID: 4006
Flags: -
Send transid: 0
Send time: 2026-06-24 13:35:32 +0200
Receive transid: 1099880
Receive time: 2026-06-24 13:35:39 +0200
Snapshot(s):
Quota group: n/a
So shouldn’t incus clear that uuid after moving/copying? Now I have to remember doing it myself or my btrfs backups will fail/complain