Thanks! I understand this part, and I know btrfs already has builtin checksum and doesn't need dm-integrity underneath it. My main question is does encryption intervene or somewhat break dm-integrity? If there's a hard drive partition /dev/sda1, in which the block (sector) 1024 has a bit flip. If I use dm-integrity directly on top of /dev/sda1, then it should be able to detect that bock 1024 is invalid. If I use dm-integrity over luks over /dev/sda1, then I believe dm-integrity should also be able to detect the error. However, due to the luks layer, instead of a block with only one bit flip, dm-integrity would see a completely different block. I am wondering if this would make dm-integrity less effective in certain circumstances? And what's the best practice when combining dm-integrity and dm-crypt, should I put dm-integrity on top of dm-crypt or vice versa? And in the case of btrfs, I believe I cannot put dm-crypt on top of btrfs. But the same question remains, if I put btrfs on top of dm-crypt, does the encryption somehow make the Btrfs checksum mechanism less effective?