omv7:omv7_plugins:zfs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
omv7:omv7_plugins:zfs [2025/10/25 01:36] – [Foreword] crashtestomv7:omv7_plugins:zfs [2025/10/25 01:43] (current) – [ZFS - General] crashtest
Line 72: Line 72:
 There are a great many misunderstandings with regard to ZFS.  This section will go over a few of them: There are a great many misunderstandings with regard to ZFS.  This section will go over a few of them:
  
-(**TL;DR** - send me to -> [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:zfs#kernels_and_their_impact|Kernels and Their Impact]].)+(**TL;DR** - **send me to** -> [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:zfs#kernels_and_their_impact|Kernels and Their Impact]].)
  
 ====  ZFS - The Memory Myth ==== ====  ZFS - The Memory Myth ====
Line 79: Line 79:
 While all use cases are not the same, for this sake of this discussion, we'll assume that users reading this document are NOT Corporate or Datacenter Admins. The assumption will be that readers are home server users, server admins for small businesses, or other entities that have 25 users or less.  In other words, when compared to Enterprise level network traffic, we're talking about relatively "light usage".\\ While all use cases are not the same, for this sake of this discussion, we'll assume that users reading this document are NOT Corporate or Datacenter Admins. The assumption will be that readers are home server users, server admins for small businesses, or other entities that have 25 users or less.  In other words, when compared to Enterprise level network traffic, we're talking about relatively "light usage".\\
 \\ \\
-The author of this document, in personal experience with running ZFS, has set up a 4TB pool on a host with 4GB of RAM and an older Atom processor (read, "a weak CPU").  File server performance for a few users, along with streaming data, was fine.  Memory might become an issue only if "dedup" (deduplication of data) is turned ON.  ("Dedup" is an Enterprise feature that is __OFF__ by default.)  In most home or small business use cases, ZFS' CPU requirements are modest.\\+The author of this document, in personal experience with running ZFS, has set up a 4TB pool on a host with 4GB of RAM and an older Atom processor (read, "a weak CPU").  File server performance for a few users, along with streaming data, is fine.  Memory might become an issue only if "dedup" (deduplication of data) is turned ON.  ("Dedup" is an Enterprise feature that is __OFF__ by default and, for home use, it is recommended that dedup remains OFF.)  In most home or small business use cases, ZFS' CPU requirements are modest.\\
 \\ \\
 **"ECC RAM is required to run ZFS".**\\ **"ECC RAM is required to run ZFS".**\\
-As is the case with most file server and NAS installations, ECC is desirable but not required.  ECC is designed to correct randomly "flipped bits" in RAM, notionally caused by cosmic rays.  While flipped RAM bits could cause an errored disk write, a more likely outcome would be a kernel or application error.  Data stored and checksummed, on a spinning hard drive or an SSD, is another matter altogether.  Correcting storage media errors is a task that ZFS handles well.\\ +As is the case with most file server and NAS installations, ECC is desirable but not required.  ECC is designed to correct randomly "flipped bits" in RAM, notionally caused by cosmic rays.  While flipped RAM bits could cause an errored disk write, a more likely outcome would be a kernel panic or an application error.  Data stored and checksummed, on a spinning hard drive or an SSD, is another matter altogether.  Maintaining error free data and correcting storage media errors and is a task that ZFS handles well.\\ 
 \\ \\
 **"ZFS is eating all of my RAM!"**\\ **"ZFS is eating all of my RAM!"**\\
  • omv7/omv7_plugins/zfs.1761356219.txt.gz
  • Last modified: 2025/10/25 01:36
  • by crashtest