From 3a0256f11d45f248db154280c1e710edb1b4f491 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 26 Sep 2016 21:34:59 +0200 Subject: [PATCH] Auto update --- faq.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/faq.html b/faq.html index 68a98e58..f440b0aa 100644 --- a/faq.html +++ b/faq.html @@ -147,7 +147,7 @@ Frequently Asked Questions for SnapRAID.
  • Why in 'sync' do I get the error 'Failed to grow parity file 'xxx' to size xxx due lack of space.'?
  • Why do I get the error 'Internal inode xxx inconsistency...'?
  • Why with .xls files do I get the error 'Data change at file...'?
    • -
  • Why are VeraCrypt/TrueCrypt containers never saved?
    • +
  • Why are VeraCrypt containers never saved?
    • @@ -1325,11 +1325,11 @@ To workaround the problem you can see or you can switch to the .xlsx format.

    -

    Why are VeraCrypt/TrueCrypt containers never saved?

    +

    Why are VeraCrypt containers never saved?

    -VeraCrypt (former TrueCrypt) by default has enabled the option Preserve modification time-stamp of file containers +VeraCrypt (a fork of TrueCrypt) by default has enabled the option Preserve modification time-stamp of file containers that makes impossible at SnapRAID, and at other backup programs, to detect that a file container is changed. -Ensure to disable this option in VeraCrypt/TrueCrypt. +Ensure to disable this option in VeraCrypt.