This seems to be btrfs with newer kernel functionality, unfortunately not described in the btrfs documentation. I found this mail list discussion … which is not good news, but also seems to be possible to remediate (with some data loss unfortunately).
https://lore.kernel.org/all/c626e033-eaec-4392-9215-b57dcb165b4e@suse.com/T/
Since this seems to be happening at the core of btrfs, I suspect nobody on the forum has a good answer for you here. What you could do is ask for help from upstream btrfs: