On Tue, 2009-04-28 at 19:37 +0200, Thomas Glanzmann wrote: > Hello Chris, > > > > Is there a checksum for every block in btrfs? > > > Yes, but they are only crc32c. > > I see, is it easily possible to exchange that with sha-1 or md5? > Yes, but for the purposes of dedup, it's not exactly what you want. You want an index by checksum, and the current btrfs code indexes by logical byte number in the disk. So you need an extra index either way. It makes sense to keep the crc32c csums for fast verification of the data read from disk and only use the expensive csums for dedup. > > > Is it possible to retrieve these checksums from userland? > > > Not today. The sage developers sent a patch to make an ioctl for > > this, but since it was hard coded to crc32c I haven't taken it yet. > > I see. > > > Yes, btrfs uses extents but for the purposes of dedup, 4k blocksizes > > are fine. > > Does that mean that I can dedup 4k blocks even if you use extents? Yes. > > > Virtual machines are the ideal dedup workload. But, you do get a big > > portion of the dedup benefits by just starting with a common image and > > cloning it instead of doing copies of each vm. > > True, the operating system can be almost completely deduped but as soon > as you start patching you loose the benefit. -chris -- 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
