On Saturday, December 28, 2019 4:05:54 AM PST you wrote:
> Doesn't this filename look familiar with previous logical-resolve output? :)
> 
> [michael@archlinux /]$ sudo btrfs ins logical-resolve 253563502592 /
> //home/michael/.mozilla/firefox/default/storage/default/https++
> +www.pinterest.com/cache/morgue/16/{b696bf53-d26a-48eb-9688-
> ab3c5fd49010}.final
> 
> The URL, the UUID, they all matches!
> 
> So yep, the file itself doesn't match its csum in the first place.
> 
> It looks like balance doesn't go regular file csum checking, but copy
> all data and all csum without verifying them, then check the csum of
> data reloc tree instead.
> 
> Thus this causes this hard-to-locate corrupted files.
> We should make it more user-friendly I guess.
> 
> 
> And obviously, just remove the offending files should allow you continue.
> 
> Thanks,
> Qu


Wow, you are right. I was worried my file system was corrupted and I'm not 
sure the exact cause leading up to this error. If there is any more debug info 
I can give you so that you can get a better idea of why this is happening, 
please let me know. 

Currently I am running balance, but I predict it will finally be able to 
complete sucessfully. However, if there are any issues I will send a reply 
here. (If I don't figure it out myself using what you just taught me)
Thanks a lot for your help. I am new to using mailing lists such as these, so 
hopefully I did everything by the rules here.
Thanks again Qu!