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:17:32 +01:00
parent 402aa54788
commit e7485c49a9
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
faq.html
View file

@ -1177,8 +1177,8 @@ The '-T largefile4' and '-m 0' options should give more space available for the
<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.
This is theoretically something that should never happen,
but in some specific conditions is instead possible.
</p>
<p>
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.
</p>
<p>
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
<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.