Explicitly note Borg v1 caching doesn't work with Btrfs (#1187).

Reviewed-on: https://projects.torsion.org/borgmatic-collective/borgmatic/pulls/1187

docs/reference/configuration/data-sources/btrfs.md

@@ -76,6 +76,14 @@ next, the [Borg file
 cache](https://borgbackup.readthedocs.io/en/stable/internals/data-structures.html#cache)
 will never get cache hits on snapshotted files. This makes backing up Btrfs
 snapshots a little slower than non-snapshotted files that have consistent paths.
+**It is also not possible to mitigate cache misses**, as the Btrfs hook uses
+snapshot paths which change between borgmatic invocations, and the snapshots
+are located outside the [runtime
+directory](https://torsion.org/borgmatic/reference/configuration/runtime-directory/),
+contrary to
+[ZFS](https://torsion.org/borgmatic/reference/configuration/data-sources/zfs/#performance)
+and
+[LVM](https://torsion.org/borgmatic/reference/configuration/data-sources/lvm/#performance).
 
 <span class="minilink minilink-addedin">With Borg version 2.x</span> Even
 snapshotted files should get cache hits, because Borg 2.x is smarter about how

docs/reference/configuration/data-sources/zfs.md

@@ -91,7 +91,7 @@ cache](https://borgbackup.readthedocs.io/en/stable/internals/data-structures.htm
 may not get cache hits on snapshotted files. This makes backing up ZFS snapshots
 a little slower than non-snapshotted files that have consistent paths. You can
 mitigate this by setting a fixed [runtime
-directory](https://torsion.org/borgmatic/reference/configuration/runtime-directory/))
+directory](https://torsion.org/borgmatic/reference/configuration/runtime-directory/)
 (that's not located in `/tmp`). This allows borgmatic to use a consistent
 snapshot path from one run to the next, thereby resulting in Borg files cache
 hits.