From 402aa54788c066f1dbecc23cceea385aa497f5d8 Mon Sep 17 00:00:00 2001
From: Andrea Mazzoleni <amadvance@gmail.com>
Date: Mon, 11 Jan 2016 19:15:46 +0100
Subject: [PATCH] Auto update

---
 faq.html | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/faq.html b/faq.html
index 92f8f877..a420303c 100644
--- a/faq.html
+++ b/faq.html
@@ -143,6 +143,7 @@ Frequently Asked Questions for <span class="bold">SnapRAID</span>.
 <ul>
 <li><a href="#oomkiller">In Linux SnapRAID aborts without any error message</a></li>
 <li><a href="#pargrowerror">Running 'sync' I get the error 'Failed to grow parity file 'xxx' to size xxx due lack of space.'</a></li>
+<li><a href="#dupinode">I get the error 'Internal inode 'xxxxxx' incosistency...'</a></li>
 </ul>
 
 
@@ -1173,6 +1174,24 @@ mkfs.ext4 -m 0 -T largefile4 DEVICE
 The '-T largefile4' and '-m 0' options should give more space available for the parity file.
 </p>
 
+<h3 id="dupinode">I get the error 'Internal inode 'xxxxxx' incosistency...'</h3>
+<p>
+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.
+</p>
+<p>
+First ensure that the mentioned files were not modified while SnapRAID was running.
+If files are renamed, deleted or recreated while SnapRAID is running, it's possible
+that inodes are reused, causing this condition.
+</p>
+<p>
+If you in Windows and you are using a FAT filesystem, try to convert it to NTFS.
+Theoretically inodes (FileIndex) are
+<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa363788%28v=vs.85%29.aspx">unique even in FAT</a>,
+but this condition was already seen in the field.
+</p>
+
 
 </div>