Daniel J Blueman <daniel.blueman@xxxxxxxxx> writes: > For purposes of data deduplication and data synchronisation, it would > be a powerful tool to expose file data checksums. > > Since eg BTRFS uses the crc32c algorithm [1], it's possible to compute > the file's overall CRC from the accumulation of the CRCs from all it's > extents' CRCs. > > For now, exposing this via an IOCTL may be sufficient, though any > ideas for introducing it in a more standard way? (it's a pity that > when stat64 was introduced, reserved fields weren't added) The problem of doing it in any "standard way" is that it would hard code the way the file system does checksums in the applications. So the file system could never change it without breaking user space. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
