Hello All, I installed the ZFS plugin and managed to add (via the OMV Plugin) a Pool, Filesystem (=Dataset) and Snapshots. I dont quite understand what adding a Volume gives me because it is nowhere visible and cannot be used for anything. Any tips?
OK, here is the trick: ZFS Volumes are block devices of defined size that can then be used by Linux to create filesystems on. Unfortunately, this doesn't work in the OMV GUI. The ZFS volume does not show under Filesystems-create new.
Does anyone know how to fix this?
Awesome: You can create filesystem on a ZFS Volume but you have to do it manually in Linux. Afterwards the Filesystem shows up in OMV !
CReate a ZFS pool called Pool2S
Create a ZFS Volume inside Pool2S with size 10MB (via OMV Plugin) called Vol10
SSH into your OMV server
mkfs -t ext4 -V /dev/zvol/Pool2S/Vol10
Now you can mount a 10MB Block Device with ETX4 filesystem inside OMV-Filesystems
Good point. I haven't found a reason yet but I am sure there is a need for it somewhere, otherwise they would have not implemented that functionality
Sorry for reviving this old thread, but I thought I'd like to contribute with a use case to the last unanswered question:
"What is the reason for to create an ext4 file system on top of an ZFS file system?"
I actually did exactly this, to host my docker storage (default /var/lib/docker), since I am using ZFS on my data drives, and USB thumbdrives as OS disks. I did not want my docker storage to reside on the OS flash drives, and also I did not want docker to have ZFS as storage, since docker will then integrate the image handling with ZFS snapshots, which will cause a mess, since my other data is then also snapshotted in a way that is outside my control.
So I created a ZVOL inside my ZFS dataset, and formatted it as ext4, mounted it as /docker, and then symlinked /var/lib/docker to /docker.
I believe I did the same as MarcS, creating the filesystem with mkfs in a shell, but instead of mounting it via OMV gui, I added the UUID to /etc/fstab, for automounting on boot.