From 4de3ca4335923fc9760d77e137cfd4c2bd8c18c9 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 11 Jan 2016 21:21:17 +0100 Subject: [PATCH] Auto update --- faq.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/faq.html b/faq.html index d5b57056..93c72add 100644 --- a/faq.html +++ b/faq.html @@ -143,9 +143,9 @@ Frequently Asked Questions for SnapRAID. @@ -1229,7 +1229,7 @@ mkfs.ext4 -m 0 -T largefile4 DEVICE The '-T largefile4' and '-m 0' options should give more space available for the parity file.

-

I get the error 'Internal inode xxx incosistency...'

+

Why do I get the error 'Internal inode xxx incosistency...'

This means that SnapRAID found two different files using the same inode. This is theoretically something that should never happen, @@ -1247,7 +1247,7 @@ Theoretically inodes (FileIndex) are but this condition was already seen in the field.

-

With .xls files I get the error 'Data change at file...'

+

Why with with .xls files do I get the error 'Data change at file...'

Unfortunately the Excel application does dirty tricks when handling .xls files, @@ -1276,7 +1276,7 @@ To workaround the problem you can see or you can switch to the .xlsx format.

-

Why TrueCrypt containers are never saved by SnapRAID?

+

Why are TrueCrypt containers never saved by SnapRAID?

TrueCrypt by default has enabled the option Preserve modification timestamp of file containers that makes impossible to SnapRAID, and other backup programs, to detect that a file container is changed.