From 1219a84753fef01f8ebdba91aa05ea4e745d54b7 Mon Sep 17 00:00:00 2001
From: James Buren <braewoods+mgh@braewoods.net>
Date: Fri, 18 Jun 2021 12:58:44 -0500
Subject: [PATCH] resolve clarify borg check --verify-data (#5808)

---
 docs/usage/check.rst.inc | 4 ++++
 src/borg/archiver.py     | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/docs/usage/check.rst.inc b/docs/usage/check.rst.inc
index e9669bbe9..7b8018f89 100644
--- a/docs/usage/check.rst.inc
+++ b/docs/usage/check.rst.inc
@@ -115,6 +115,10 @@ Second, the consistency and correctness of the archive metadata is verified:
 - In repair mode, when all the archives were checked, orphaned chunks are deleted
   from the repo. One cause of orphaned chunks are input file related errors (like
   read errors) in the archive creation process.
+- In verify-data mode, a complete cryptographic verification of the archive data
+  integrity is performed. This conflicts with ``--repository-only`` as this mode
+  only makes sense if the archive checks are enabled. The full details of this mode
+  are documented below.
 - If checking a remote repo via ``ssh:``, the archive check is executed on the
   client machine because it requires decryption, and this is always done client-side
   as key access is needed.
diff --git a/src/borg/archiver.py b/src/borg/archiver.py
index bcae215f7..db34c370c 100644
--- a/src/borg/archiver.py
+++ b/src/borg/archiver.py
@@ -3127,6 +3127,10 @@ class Archiver:
         - In repair mode, when all the archives were checked, orphaned chunks are deleted
           from the repo. One cause of orphaned chunks are input file related errors (like
           read errors) in the archive creation process.
+        - In verify-data mode, a complete cryptographic verification of the archive data
+          integrity is performed. This conflicts with ``--repository-only`` as this mode
+          only makes sense if the archive checks are enabled. The full details of this mode
+          are documented below.
         - If checking a remote repo via ``ssh:``, the archive check is executed on the
           client machine because it requires decryption, and this is always done client-side
           as key access is needed.