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-03-01 22:29:21 +01:00
parent 89aa55b15e
commit bbcbd85855
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
faq.html
View file

@ -125,6 +125,7 @@ Frequently Asked Questions for <span class="bold">SnapRAID</span>.
<li><a href="#syncaccess">Does SnapRAID allow to access data disks during a 'sync'?</a></li>
<li><a href="#retryop">Does SnapRAID retry reads or writes if a disk is not working?</a></li>
<li><a href="#lock">What's the snapraid.content.lock file?</a></li>
<li><a href="#subsecond">What's the notice about zero sub-second timestamp?</a></li>
</ul>
@ -1089,6 +1090,23 @@ It's a file used by SnapRAID to check if another SnapRAID instance is already ru
It's created where the first content file is placed.
</p>
<h3 id="subsecond">What's the notice about zero sub-second timestamp?</h3>
<p>
In the status command you may now get a notice like:
</p>
<pre>
You have XXXXX files with zero sub-second timestamp.
Run the 'touch' command to set it to a not zero value.
</pre>
<p>
It means that a number of your files have a timestamp approximated at the second value,
when instead your filesystem can store a more precise timestamp, with a sub-second precision.
This is not a problem by itself, but it could limit the SnapRAID effectiviness when detecting
moved or copied files.
You have the option to set that subsecond timestamp to a random value using the new 'touch' command.
Note that the second part of the timestamp is not modified.
</p>
<h2>Performance</h2>
<h3 id="perfhardware">Which is the optimal hardware configuration to get the best performance?</h3>