From ca2f8b09892095a5d5d028e649af830838ae5ff6 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 22 Jan 2024 21:58:41 +0100 Subject: [PATCH] Auto update --- manual.html | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/manual.html b/manual.html index 222f0ca7..6c2f20ba 100644 --- a/manual.html +++ b/manual.html @@ -140,33 +140,33 @@ consider before using it.

The main one is that if a disk fails, and you haven't recently synced, you may be unable to do a complete recover. -More specifically, you may be unable to recover up to the size of the -amount of the changed or deleted files from the last sync operation. +More specifically, you may be unable to recover up to the size of +the changed or deleted files from the last sync operation. This happens even if the files changed or deleted are not in the -failed disk. This is the reason because SnapRAID is better suited for +failed disk. This is why SnapRAID is better suited for data that rarely change.

-Instead the new added files don't prevent the recovering of the already -existing files. You may only lose the just added files, if they are on +On the other hand, newly added files don't prevent recovering already +existing files. You may only lose the recently added files, if they are on the failed disk.

-Other limitations are: +Other SnapRAID limitations are: