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:59:44 +01:00
parent ef90978fd9
commit 86f038d183
1 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

10
faq.html
View file

@ -443,17 +443,19 @@ For the data disks, follow these suggestions:
<td>OK. In general you can use whatever filesytem you like. Just see the following notes for some exceptions.</td>
</tr>
<td>Btrfs</td>
<td>OK. But ensure to build SnapRAID with the libblkid library to get UUID support. You will be warned if this doesn't happen.</td>
<td>OK. But ensure to build SnapRAID with the libblkid library to get UUID support.
You will be warned at every run if this doesn't happen.</td>
</tr>
<tr>
<td>ReiserFS</td>
<td>Unsure. Where are <a href="https://sourceforge.net/p/snapraid/discussion/1677233/thread/194dee16">reports</a> of speed increase when switching from ReiserFS to other filesystem.
<td>Unsure. Where are <a href="https://sourceforge.net/p/snapraid/discussion/1677233/thread/194dee16">reports</a>
of speed increase when switching from ReiserFS to other filesystem.
ext4 and XFS are anyway better. Use them insted.</td>
</tr>
<tr>
<td>FAT</td>
<td>Unsure. There are <a href="https://sourceforge.net/p/snapraid/discussion/1677233/thread/455e8d63">reports</a> of duplicate inodes cases.
NTFS is anyway a lot faster. Use it insted.</td>
<td>Unsure. There are <a href="https://sourceforge.net/p/snapraid/discussion/1677233/thread/455e8d63">reports</a>
of duplicate inodes cases. NTFS is anyway a lot faster. Use it insted.</td>
</tr>
</table>