docs_in_draft: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
docs_in_draft:zfs [2022/08/05 15:13] crashtestdocs_in_draft:zfs [2025/03/08 03:31] (current) – [Installation] crashtest
Line 8: Line 8:
 {{ :omvextras_logo4.jpg?400 |}} {{ :omvextras_logo4.jpg?400 |}}
  
-====== ZFS Plugin For OMV6 ======+====== ZFS Plugin For OMV7 ======
 \\ \\
 \\ \\
Line 14: Line 14:
 ===== Summary ===== ===== Summary =====
  
-The ZFS plugin makes it easy for users to take advantage of ZFS by installing ZFS and making it's more important features available within Openmediavault's GUI.  +The ZFS plugin makes it easy for users to take advantage of ZFS, with an easy installation and making ZFS's more important features available within Openmediavault's GUI.  
  
 ==== What is ZFS? ==== ==== What is ZFS? ====
  
-ZFS is an advanced "Copy on Write" file system with several desirable features+ZFS (the Zettabyte File System) is the oldest of the "Copy on Write" file system.  It has been under continuous development since it introduced, with Solaris, in 2001.
  
 The more important among ZFS' several features are as follows: The more important among ZFS' several features are as follows:
  
   *     Pooled storage (Built in logical volume management)   *     Pooled storage (Built in logical volume management)
-  *     **Snapshots**  (Creates file, folder, volume history.) +  *     **Snapshots**  (Creates file, folder, filesystem and volume histories.) 
-  *     Data **integrity verification** and **automatic repair** +  *     Data **integrity verification** and, with zmirrors or with activation of the 2copies feature, **automatic repair** 
-  *     RAID-Z, Zmirror and other legacy RAID equivalents, without legacy drawbacks such as the "write hole" and silent data corruption.  +  *     RAID-Z, Zmirror and other implementations of ZFS are the functional equivalents to legacy RAID, without legacy RAID drawbacks such as the "write hole" and silent data corruption.
  
 Data integrity and repair, and data restoration (VIA snapshots) are among ZFS' more important features. Data integrity and repair, and data restoration (VIA snapshots) are among ZFS' more important features.
Line 49: Line 49:
 ===== Prerequisites ===== ===== Prerequisites =====
  
-  * [[https://wiki.omv-extras.org/doku.php?id=misc_docs:omv_extras|OMV-Extras]] must be pre-installed.  +  * [[https://wiki.omv-extras.org/doku.php?id=misc_docs:omv_extras|OMV-Extras]] must be pre-installed
 +  * [[https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html|PuTTY]] is an SSH client that will allow users to connect to their SBC, from a Windows client, and get on the command line.  PuTTY is installable on a Windows client.  
  
  
 ===== Installation ===== ===== Installation =====
  
-To get started with ZFS and create the most stable server possible, some preliminary settings and adjustments are recommended.+To get started with ZFS and to create an easy installation path to the most stable server possible, some preliminary setup, settings and adjustments are recommended.
  
-Disable Backports:\\ +==== Disable Backports: ==== 
-Linux backport kernels are released quickly to support the "latest and greatest - cutting edgehardware.  As a consequence the "userland" (software supported by the latest backport kernels) may not be complete.  ZFS at times, may not be in the software repo's of backports kernels, immediately after their release.  To avoid broken package issues it's best to use the mainline kernel, by disabling "backports". \\+ 
 +=== General: === 
 +Linux backport kernels are released quickly to support the "latest and greatest - cutting edge hardware".  As a consequence the "userland" (software supported by the latest backport kernels) may not be complete.  ZFSat times, may not be in the software repo's of backports kernels, immediately after their release.  This may result in a kernel upgrade where a server's ZFS pool(s) may disappear.  There are remedies for this but an ounce of prevention is worth a pound of cure. To avoid broken package issues it's best to use the mainline kernel, by disabling "backports". \\ 
 +\\ 
 +==== Install the Proxmox kernel: ====
 \\ \\
-Install the Proxmox kernel:\\ +=== General=== 
-Due to licsensing conflicts, Debian does not build ZFS modules into any of their kernels by default.  The+Due to licensing conflicts, Debian does not build ZFS kernel modules into any of their kernels by default.  This may result in an extensive build process, during the installation of ZFS, which is prone to errors.  These issues can be avoided by using the Proxmox-Debian kernel which has ZFS kernel modules preinstalled by default.  As Proxmox kernel upgrades become available and are performed, the repo's for the Proxmox kernel will always have the required packages to support ZFS.  Further, since the Proxmox kernel is financially supported by the Proxmox project, the kernel is exhaustively tested before it's made available.  In the bottom line, using the Proxmox kernel decreases the possibility of an installation error while increasing overall server reliability and providing .   a default.     as   However, the Proxmox kernel
  
  
  • docs_in_draft/zfs.1659712404.txt.gz
  • Last modified: 2022/08/05 15:13
  • by crashtest