[HOWTO] Instal ZFS-Plugin & use ZFS on OMV

    • OMV 1.0
    • Hi! Can you help me with some error? I'm tried to install zfs support.
      I'm do:
      install OMV-extras 5 openmediavault-omvextrasorg_latest_all5.deb
      i cant find this forum.openmediavault.org/index…2092-Enable-ZFS-Repo-jpg/
      and just enable test, backports and extras repo.
      then, i'm tried install openmediavault-zfs 5.0.1 plugin, but i have some errors on this point.
      full log in attach.

      Source Code

      1. dpkg: error processing package zfs-zed (--configure):
      2. dependency problems - leaving unconfigured
      3. Processing triggers for libc-bin (2.28-10) ...
      4. Processing triggers for systemd (241-7~deb10u2) ...
      5. Processing triggers for openmediavault (5.1.2-1) ...
      6. Restarting engine daemon ...
      7. Errors were encountered while processing:
      8. zfsutils-linux
      9. openmediavault-zfs
      10. zfs-zed
      i.imgur.com/lZZ1xxm.png my system
      sorry for russian.
      Please, help me)
      Files
      • zfs error.txt

        (9.81 kB, downloaded 20 times, last: )
    • Hi, I'm on Proxmox kernel and I have the openmediavault-zfs plugin. My host is running Proxmox and OMV is running in a VM.

      I have a zpool called MyData which I created on the Proxmox host and have since exported. I am trying to import it in the OMV VM but I get the following error:

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; zpool import "MyData" 2>&1' with exit code '1': cannot import 'MyData': unsupported version or feature This pool uses the following feature(s) not supported by this system: org.zfsonlinux:project_quota (space/object accounting based on project ID.) com.delphix:spacemap_v2 (Space maps representing large segments are more efficient.) All unsupported features are only required for writing to the pool. The pool can be imported using '-o readonly=on'.

      I get the same error regardless of whether I try the import from the shell or from the GUI.

      Here's the output from running it in the shell, because it's easier to read:

      Source Code

      1. root@nas:~# zpool import -f MyData
      2. This pool uses the following feature(s) not supported by this system:
      3. org.zfsonlinux:project_quota (space/object accounting based on project ID.)
      4. com.delphix:spacemap_v2 (Space maps representing large segments are more efficient.)
      5. All unsupported features are only required for writing to the pool.
      6. The pool can be imported using '-o readonly=on'.
      7. cannot import 'MyData': unsupported version or feature

      The post was edited 2 times, last by Haystack ().

    • Yes it is stable enough, just watch out that there is no more docker plugin, but instead you have portainer.
      As for the upgrade, you can try:
      sed -i "s/stretch/buster/g" /etc/apt/sources.list
      sed -i "s/stretch/buster/g" /etc/apt/sources.list.d/*
      sed -i "s/arrakis/usul/g" /etc/apt/sources.list.d/*
      apt-get update
      apt-get dist-upgrade
      reboot

      As always backup etc etc.
    • Hello,
      I am not sure if this is the right place to ask this question. I tried to search in the forums but cannot seem to find the answer.
      I have been using OMV for backup purposes only for about a year now and I decided to consolidated my home server inside OMV.
      I upgraded to OMV 5 and added a ZFS mirrored disk. I have the OMV base files on an SSD and all my data on the ZFS pool.
      I went ahead and added docker and kvm and pretty much everything seems to be working but . . .
      I ran into the "common problem" that people experience with the shared folders not saving. see attached.
      I am not sure if its related to my docker setup but I read a post that the recommendation is to use the "srv" mounts for the volumes in the container.
      I don't see this in ZFS. I am not sure if my I have my ZFS + docker setup is correct. I also noticed that docker is creating a zfs mount for the graph.
      omvstor1/8bb66d1f5d4d3c0f8f101eedc257090225bb64f16d7844e6078e5f933600eadb on /sharedfolders/docker/zfs/graph/8bb66d1f5d4d3c0f8f101eedc257090225bb64f16d7844e6078e5f933600eadb type zfs (rw,relatime,xattr,noacl)

      setup:

      {
      "data-root": "/omvstor1/dockerFiles"
      }

      Linux openmediavault.devsphoto.com 5.3.13-1-pve #1 SMP PVE 5.3.13-1 (Thu, 05 Dec 2019 07:18:14 +0100) x86_64 GNU/Linux
      Files
      • omv error.txt

        (33.24 kB, downloaded 5 times, last: )
    • freebsd wrote:

      I read a post that the recommendation is to use the "srv" mounts for the volumes in the container.
      I don't see this in ZFS.
      This doesn't apply to ZFS. When you name the pool, with default settings, the mount point is the name of the pool. Generally, this location will be at the root of the boot drive. (In my case the pool names is /ZFS1 )






      The only thing that comes to mine, regarding Dockers and ZFS, is that you don't want to store Docker images and containers on a ZFS drive filesystem. Docker uses overlayfs which past versions of ZFS interpreted as being legacy filesystem clones.

      Since you're booting from an SSD, it would be best to keep your Docker images and containers there, in the default location.
      In OMV4, the default Docker location is /var/lib/docker
    • crashtest wrote:

      freebsd wrote:

      I read a post that the recommendation is to use the "srv" mounts for the volumes in the container.
      I don't see this in ZFS.
      This doesn't apply to ZFS. When you name the pool, with default settings, the mount point is the name of the pool. Generally, this location will be at the root of the boot drive. (In my case the pool names is /ZFS1 )





      The only thing that comes to mine, regarding Dockers and ZFS, is that you don't want to store Docker images and containers on a ZFS drive filesystem. Docker uses overlayfs which past versions of ZFS interpreted as being legacy filesystem clones.

      Since you're booting from an SSD, it would be best to keep your Docker images and containers there, in the default location.
      In OMV4, the default Docker location is /var/lib/docker
      ok. I will have to investigate how much data this filesystem (/var/lib/docker)uses since I only have 120GB ssd for my OMV base. I assume the "volumes" can still be stored on my zpool.
    • freebsd wrote:

      I assume the "volumes" can still be stored on my zpool
      You can point your volumes and bind points to the ZFS pool and you should. (The output of a downloader, for example.)

      It's the Docker containers themselves that need to be installed/stored somewhere other than in a ZFS pool. Docker images and containers are usually just a few meg's each. They're really bare-bones. A 120GB SSD should be more than enough, so the default Docker location should be fine. Some users are running Dockers on USB thumbdrives in the 16 to 32GB range without issues.

      However if you're using Plex in a Docker and have a large library, you should consider moving Plex's meta-database storage to the pool. It can become quite large. There's info on the forum, and on the Plex web site, on how to do that.