On 29/01/2025 15.02, Kanchan Joshi wrote:
TL;DR first: this makes Btrfs chuck its checksum tree and leverage NVMe SSD for data checksumming. Now, the longer version for why/how. End-to-end data protection (E2EDP)-capable drives require the transfer of integrity metadata (PI). This is currently handled by the block layer, without filesystem involvement/awareness. The block layer attaches the metadata buffer, generates the checksum (and reftag) for write I/O, and verifies it during read I/O.
May be this is a stupid question, but if we can (will) avoid storing the checksum in the FS, which is the advantage of having a COW filesystem ? My understand is that a COW filesystem is needed mainly to synchronize csum and data. Am I wrong ? [...] BR -- gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
