rt/snapraid
1
0
Fork 0
mirror of https://github.com/amadvance/snapraid.git synced 2026-10-26 19:01:57 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Auto update

Browse source
This commit is contained in:
Andrea Mazzoleni 2016-01-11 19:15:46 +01:00
parent f13ce72aad
commit 402aa54788
1 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
faq.html
View file

@ -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>