From 25b9c6cf454ceb8de5824ce07382b9106e7ccdba Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 11 Jan 2016 19:55:52 +0100 Subject: [PATCH] Auto update --- faq.html | 26 ++++++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/faq.html b/faq.html index c281ca07..4a3d0e82 100644 --- a/faq.html +++ b/faq.html @@ -433,12 +433,34 @@ Some interesting articles about number of parity levels and failure rate of disk

Which filesystem is recommended for SnapRAID ?

-For the data disks, you can use whatever filesystem you like. +For the data disks, follow these suggestions: +

+ + + + + + + + + + + + + + + + + +
Data FileSystemResult
AnyOK. In general you can use whatever filesytem you like. Just see the following notes for some exceptions.
BtrfsOK. But ensure to build SnapRAID with the libblkid library to get UUID support. You will be warned if this doesn't happen.
ReiserFSUnsure. Where are user reports reporting speed increase when switching from ReiserFS to other filesystem. +
FATUnsure. There are resports of duplicate inodes cases. NTFS is anyway a lot faster. Use it insted.
+ +

For the parity disks, follow these suggestions:

- +
FileSystemResult
Parity FileSystemResult
ext3 No. It doesn't support the fallocate() command needed to allocated the parity files.