Explorar el Código

Merge pull request #5859 from braewoods/check_notice

add notice about defective hardware to check documentation (#5753)
TW hace 4 años
padre
commit
9d59255611
Se han modificado 2 ficheros con 10 adiciones y 0 borrados
  1. 5 0
      docs/usage/check.rst.inc
  2. 5 0
      src/borg/archiver.py

+ 5 - 0
docs/usage/check.rst.inc

@@ -87,6 +87,11 @@ The check command verifies the consistency of a repository and the corresponding
 check --repair is a potentially dangerous function and might lead to data loss
 check --repair is a potentially dangerous function and might lead to data loss
 (for kinds of corruption it is not capable of dealing with). BE VERY CAREFUL!
 (for kinds of corruption it is not capable of dealing with). BE VERY CAREFUL!
 
 
+Pursuant to the previous warning it is also highly recommended to test the
+reliability of the hardware running this software with stress testing software
+such as memory testers. Unreliable hardware can also lead to data loss especially
+when this command is run in repair mode.
+
 First, the underlying repository data files are checked:
 First, the underlying repository data files are checked:
 
 
 - For all segments, the segment magic header is checked.
 - For all segments, the segment magic header is checked.

+ 5 - 0
src/borg/archiver.py

@@ -3099,6 +3099,11 @@ class Archiver:
         check --repair is a potentially dangerous function and might lead to data loss
         check --repair is a potentially dangerous function and might lead to data loss
         (for kinds of corruption it is not capable of dealing with). BE VERY CAREFUL!
         (for kinds of corruption it is not capable of dealing with). BE VERY CAREFUL!
 
 
+        Pursuant to the previous warning it is also highly recommended to test the
+        reliability of the hardware running this software with stress testing software
+        such as memory testers. Unreliable hardware can also lead to data loss especially
+        when this command is run in repair mode.
+
         First, the underlying repository data files are checked:
         First, the underlying repository data files are checked:
 
 
         - For all segments, the segment magic header is checked.
         - For all segments, the segment magic header is checked.