Google brought me to this old thread because I get the exact same failed csum errors on my btrfs: "csum 0x2ac15d26"
And it looks like we have the same model drive: Seagate Barracuda Compute ST8000DM004-2CX188
These cheap SMR clearly have some systematic problem which manifests occasionally as poorly written, then unreadable bytes. I would guess that 0x2ac15d26 is the shash_digest of all 0x00s or 0xFFs. The drive itself never reports any problem -- SMART tests always succeed.
As a workaround I run scrub weekly on this FS -- it finds and fixes a few hundred errors each time (always on newly written data).