We are still actively working on the spam issue.
Difference between revisions of "Home Server/Setting up your Storage"
m |
m |
||
| Line 9: | Line 9: | ||
== See also == | == See also == | ||
| − | [[Home server]] | + | *[[Home server]] |
| − | [[Storage | + | *[[Storage devices]] |
Revision as of 21:21, 22 December 2020
ZFS has a lot of really great features that make a a superb file system. It has file system level checksums for data integrity, file self healing which can correct silent disk errors, incremental snapshots and rollback, file deduplication, encryption, and more.
There are however, some downsides to ZFS. Notably inflexibility and the upfront cost. ZFS RaidZ arrays CANNOT BE EXPANDED after being created. Parity cannot be added either (you cannot change a RaidZ1 to a RaidZ2 later on). You cannot use differently sized disks or disks with data already on them, even disks formatted as ZFS. In other words, you need to buy ALL of the disks you plan on using in your RaidZ array at the same time, because unlike other software raid (or even hardware raid), you won't be able to change it later. This inherently makes ZFS costly to use and thus unfriendly to more budget oriented server builds. Now also add in the fact that running ZFS also requires a hefty amount of RAM, preferably ECC ram, which is expensive in and of itself and requires server hardware to utilise to it's fullest, and that some of the fancy features like dedup also require a good processor too... The price tag starts to add up really quickly.
So when asking yourself "Should I use ZFS?" you really should be asking "Do I really need ZFS?" (Do I want long term data integrity and all those other fancy features?) and "Can I afford ZFS?". If the answer to both of those questions is "Yes", then you can and should use ZFS, otherwise use something else like Snapraid or mdadm.
