From ea0e7d4867ae3af3dbe7a389fa31a1ffadcc0a5f Mon Sep 17 00:00:00 2001 From: Kayot Date: Tue, 25 Aug 2015 23:35:18 -0400 Subject: [PATCH] Jump Links fixed. --- pooling.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pooling.md b/pooling.md index 63a00d1..13db4cb 100644 --- a/pooling.md +++ b/pooling.md @@ -1,7 +1,7 @@ # Pooling Drives - * [Linux Solutions](pooling#Linux) - * [Windows Solutions](pooling#Windows) + * [Linux Solutions](pooling#linux) + * [Windows Solutions](pooling#windows) ## Linux There are two main ways to pool drives in Linux that are favorable to using SnapRAID. The first is AUFS (Another Unified File System) and the second and probably better choice is mhddfs (Multi Hard Disk Device File System). Both are FUSE (Filesystem in Userspace) which typically means slower. However, as computers get faster and faster, the limitations with FUSE have gone away. The idea is that the file system interacts with the users pace layer, then the hardware layer and then from the hardware into the user space layer, adding a step both ways on each operation causing a massive slow down. Again, on decent hardware such as a Xeon E3-1220V3 with 8+ GB of ECC ram, this isn't going to bottleneck the process. Now if you are using this on a Raspery Pi, then you've made a poor choice in your NAS (Network Attached System).