DOC: Clarify clone vs reflink

Clone maintains metadata of both files, while reflink deletes one and replaces it with a reflink. See [What does a rmlint's “clone” for btrfs do?](https://unix.stackexchange.com/a/428253) on Unix StackExchange
sahib · Jun 5, 2021 · 0b4e6db · 0b4e6db
1 parent 5f058ea
commit 0b4e6db
Showing 1 changed file with 5 additions and 4 deletions.
diff --git a/docs/tutorial.rst b/docs/tutorial.rst
@@ -311,10 +311,11 @@ Here's the list of currently available formatters and their config options:
 
     - *clone*: reflink-capable filesystems only. Try to clone both files with the
       FIDEDUPERANGE ``ioctl(3p)`` (or BTRFS_IOC_FILE_EXTENT_SAME on older kernels).
-      This will free up duplicate extents. Needs at least kernel 4.2.
-    - *reflink*: Try to reflink the duplicate file to the original. See also
-      ``--reflink`` in ``man 1 cp``. Fails if the filesystem does not support
-      it.
+      This will free up duplicate extents while preserving the metadata of both. 
+      Needs at least kernel 4.2.
+    - *reflink*: Try to replace the duplicate file with a reflink to the original. 
+      See also ``--reflink`` in ``man 1 cp``. Fails if the filesystem does not 
+      support it.
     - *hardlink*: Replace the duplicate file with a hardlink to the original
       file. Fails if both files are not on the same partition.
     - *symlink*: Tries to replace the duplicate file with a symbolic link to