From e7485c49a9385d4158f40c02fe09b3f40deb8160 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 11 Jan 2016 19:17:32 +0100 Subject: [PATCH] Auto update --- faq.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/faq.html b/faq.html index a420303c..05c26824 100644 --- a/faq.html +++ b/faq.html @@ -1177,8 +1177,8 @@ The '-T largefile4' and '-m 0' options should give more space available for the

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

This means that SnapRAID found two different files using the same inode. -This is theoretically an impossible condition, but in some specific conditions -is instead possible. +This is theoretically something that should never happen, +but in some specific conditions is instead possible.

First ensure that the mentioned files were not modified while SnapRAID was running. @@ -1186,7 +1186,7 @@ If files are renamed, deleted or recreated while SnapRAID is running, it's possi that inodes are reused, causing this condition.

-If you in Windows and you are using a FAT filesystem, try to convert it to NTFS. +If you are using a FAT filesystem in Windows, try to convert it to NTFS. Theoretically inodes (FileIndex) are unique even in FAT, but this condition was already seen in the field.