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 [2025/03/27 00:18] – [ZFS - The "Licensing" Issue] crashtestdocs_in_draft:zfs [2025/04/26 01:01] (current) – [Install the Proxmox kernel:] crashtest
Line 65: Line 65:
  
 === The Debian Backports Kernel === === The Debian Backports Kernel ===
-The Backports Kernel (default) is used, primarily for it's support of the latest hardware and, along similar lines, for the latest software packages.  The issue with the backports kernel, where ZFS is concerned, is that it's possible to have a kernel upgrade offered for installation that does not have ZFS packages in it'repo's.  (This has happened, to the author of this doc.)  After such an upgrade, this may result in a ZFS pool "disappearing" The pool still exists but, "fixing the issue" requires booting into an older kernel to see the pool until the new kernels packages "catch up" For this reason alone, the backports kernel is not recommended.+The Backports Kernel (OMV'default kernel) is used, primarily for it's support of the latest hardware and, along similar lines, for the latest software packages.  The issue with the backports kernel, where ZFS is concerned, is that it's possible to have a kernel upgrade offered for installation that does not have ZFS packages in its repo's.  (This has happened, to the author of this doc.)  After a kernel upgrade, this may result in a ZFS pool "disappearing" The pool still exists but, "fixing the issue" requires booting into an older kernelto see the pooluntil the new kernels packages "catch up" For this reason alone, the backports kernel is not recommended.
  
 === The Standard Debian Kernel === === The Standard Debian Kernel ===
-The Standard Debian Kernel (selectable) can be used for ZFS.  However, since ZFS kernel modules are not installed by default, they must be built by the ZFS plugin.  While this will work, building the modules is a long process that requires access to online repo's.  Accordingly, it is prone to errors.  The Standard Kernel is very usablefor ZFS, but not ideal.+The Standard Debian Kernel (selectable) can be used for ZFS.  However, since ZFS kernel modules are not installed by default, they must be built by the ZFS plugin.  While this process works, building the modules is a long process that requires continuous access to online repo's.  Accordingly, the potential for a build error exists.  For this reason, while the Standard Kernel is very usable for ZFS, it is not ideal.
  
 === The Proxmox Kernel === === The Proxmox Kernel ===
-The Proxmox Kernel is a Ubuntu Kernel that has ZFS modules prebuilt and compiled in the kernel by default.  However, the Kernel plugin is required to install the Proxmox Kernel.  Among the other useful features available, the kernel module will pull and install a Proxmox kerneland can make it the default when booting.  As Proxmox kernel upgrades become available and are performed, the repo's for the kernel will always have the required packages to support ZFS.  Further, since the Proxmox kernel is financially supported by the [[https://www.proxmox.com/en/|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 and guarantees ZFS support while increasing overall server reliability.+The Proxmox Kernel is a Ubuntu Kernel that has ZFS modules prebuilt and compiled into the kernel by default.  However, the **Kernel plugin** is required to install the Proxmox Kernel.  Among the other useful features available, the kernel module will pull and install a Proxmox kernel and make it the default kernel when booting.  As Proxmox kernel upgrades become available and are performed, the repo's for the kernel will always have the required packages to support ZFS.  Further, since the Proxmox kernel is financially supported by the [[https://www.proxmox.com/en/|Proxmox Virtualization project]], the kernel is exhaustively tested, with ZFS modules installed, before it's made available to the public.  In the bottom line, using the Proxmox kernel decreases the possibility of an installation error and guarantees ZFS support while increasing overall server reliability.\\ 
 +\\ 
 +=== Kernels for ZFS Support - The Bottom line === 
 +\\ 
 +ZFS with the backports Debian kernel - this is a bad idea. Problems are possible with each backports kernel update.\\ 
 +ZFS with the standard Debian kernel - this combination will work, but it's not ideal.\\ 
 +ZFS with the Proxmox kernel - this is the best case scenario for ZFS.\\ 
 +\\ 
  
  
Line 78: Line 86:
 ===== Installation ===== ===== Installation =====
  
-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.+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.\\ 
 +\\ 
 +At this point, a user choice must be made: 
 +  * If the Standaard Debian kernel is to be used, proceed with [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:zfs#disable_backports|Disable Backports below]] . 
 +  * If the Proxmox kernel is to be used, skip to -> [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:zfs#install_the_proxmox_kernel|Install The Proxmox Kernel]].\\ 
 +\\ 
 +----
  
 ==== Disable Backports: ==== ==== Disable Backports: ====
  
-=== General=== +As previously mentioned in [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:zfs#the_debian_backports_kernel|The Debian Backports Kernel]], in preparing to install ZFSdisabling backports is highly recommend.\\ 
-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 ZFS, at timesmay not be in the software repo's of backports kernelsimmediately after their release This may result in a kernel upgrade where server's ZFS pool(s) may disappear.  There are remedies for this but an ounce of prevention is worth a pound of cureTo avoid broken package issues it'best to use the mainline kernel, by disabling "backports". \\+\\ 
 +Under **System**, **OMV-Extras**, click on **Disable backports**\\ 
 +(This may take few minutes to complete.  At the end of the process, **End of Line** will appear and the **Close** button will activate.)\\ 
 +\\ 
 +{{ :omv7:omv7_plugins:zfs-01.jpg?nolink&600 |}} 
 +\\ 
 +\\ 
 +Since the above process changes repo's, click on **apt clean repos** and **apt clean**.\\ 
 +While it'not absolutely necessary, to insure that the standard Debian kernel and it's repo's are alignedconsider rebooting the server before proceeding.\\ 
 +\\ 
 + 
 \\ \\
 ==== Install the Proxmox kernel: ==== ==== Install the Proxmox kernel: ====
 \\ \\
 +Under **System**, **Kernel**, select the download **Proxmox** icon and select a **kernel**.\\
 +(While this selection is the users choice, the oldest kernel may result in an avoidable upgrade in the near future while the newest kernel is not as well tested in the field conditions.)\\
 +\\
 +{{ :omv7:omv7_plugins:zfs-02.jpg?nolink&600 |}}
 +\\
 +The dialog box will recommend rebooting to complete the installation of the Proxmox kernel.  Reboot now.\\
 +\\
 +After the reboot is complete, under **System**, **Update Management**, **Updates**, check for updates. It is likely that Proxmox related updates will be available.  Install these updates.\\
 +\\
 +----
 +
 +
 +   
 === General: === === General: ===
 place holder place holder
  • docs_in_draft/zfs.1743034731.txt.gz
  • Last modified: 2025/03/27 00:18
  • by crashtest