Hi Richard, > It is interesting that for me the number of extents before and after > bcache are essentially the same. > > The lesson here for me there is that the fragmentation of a btrfs > nodatacow file is not mitigated by bcache. There seems to be nothing I > can do to prevent that fragmentation, and may in fact be expected > behavior.
This is to be expected - bcache behaves like a single, transparent block device - so for btrfs it doesn't matter whether you run on a "real" device or a bcache one. The performance increase is expected, however ;) Best regards, Clemens -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
