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/06/25 03:18] – [VDEV Types] crashtestomv7:omv7_plugins:zfs [2025/06/26 12:27] (current) – [Additional Reading] crashtest
Line 76: Line 76:
 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").  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.  (This 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, was fine.  Memory might become an issue only if "dedup" (deduplication of data) is turned ON.  (This is an Enterprise feature that is __OFF__ by default.)  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".**\\
Line 200: Line 200:
 \\ \\
 <html><center>After the reboot, under <b>System</b>, <b>Kernel</b>:</center></html> <html><center>After the reboot, under <b>System</b>, <b>Kernel</b>:</center></html>
-\\ 
 <html><center>Only Proxmox kernels should be displayed (ending with <b>-pve</b>), along with memory testing utilities and other utilities that may have been previously installed.</center></html> <html><center>Only Proxmox kernels should be displayed (ending with <b>-pve</b>), along with memory testing utilities and other utilities that may have been previously installed.</center></html>
  
Line 225: Line 224:
  
  
-- A ZFS "**Pool**" is made up of one or more "**VDEV**'s".  More detailed information on VDEVs can be found -> [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:zfs#vdev_types|here]].  It's recommended that new ZFS users review the various VDEV types as the selections made during the following steps will have an impact on future Pool maintenance and expansions.\\+- A ZFS "**Pool**" is made up of one or more "**VDEV**'s".  More detailed information on VDEVs can be found -> [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:zfs#vdev_types|here]].  It's recommended that new ZFS users review the various VDEV types as the selections made during the following steps will have an impact on future Pool maintenance and expansions.\\
 - During the creation of a "Pool", in accordance with user selections, the installation process creates and adds the first VDEV automatically.\\ - During the creation of a "Pool", in accordance with user selections, the installation process creates and adds the first VDEV automatically.\\
 - A Pool can have one or more VDEVs and a new VDEV can be added to an existing pool, at any time, increasing the pool's size.\\ - A Pool can have one or more VDEVs and a new VDEV can be added to an existing pool, at any time, increasing the pool's size.\\
Line 319: Line 318:
 ---- ----
 \\ \\
-<html><center>In the <b>Add</b> dialog box, give the Filesystem a name, and click <b>Add</b>.</center></html>+<html><center>In the <b>Add</b> dialog box, under <b>Type</b> select <b>Filesystem</b>, give the Filesystem a name, and click <b>Add</b>.</center></html>
 \\ \\
 \\ \\
Line 503: Line 502:
 - While copies=2 can be used with a Basic volume, it should be noted that in the event of a disk failure both file copies would be lost.  However, if data integrity and automatic restoration is used at the primary server, data on a backup server would be clean.\\ - While copies=2 can be used with a Basic volume, it should be noted that in the event of a disk failure both file copies would be lost.  However, if data integrity and automatic restoration is used at the primary server, data on a backup server would be clean.\\
 - RAID-Z implementations reconstruct errored data a bit differently.  While some data reconstruction is possible, using parity calculations, RAID-Z does not provide for restoration of //silent// errors.  While RAID-Z provides __disk__ redundancy, copies=2 would be required to provide for __maximum__ data protection and file restoration.\\ - RAID-Z implementations reconstruct errored data a bit differently.  While some data reconstruction is possible, using parity calculations, RAID-Z does not provide for restoration of //silent// errors.  While RAID-Z provides __disk__ redundancy, copies=2 would be required to provide for __maximum__ data protection and file restoration.\\
 +\\
 +----
 +\\
 +==== Additional Reading ====
 +
 +The following link features Arron Topance's excellent [[https://tadeubento.com/2024/aarons-zfs-guide/|ZFS guide]].
 +\\
 +For a deep dive into ZFS and its internals -> [[https://openzfs.github.io/openzfs-docs/|OpenZFS Documentation]].\\
 +\\
 +
 + 
  
  
  • omv7/omv7_plugins/zfs.1750821509.txt.gz
  • Last modified: 2025/06/25 03:18
  • by crashtest