steini84

The problem is with using a newer version of zfs than 2.0.0. I tried saving the img file on ZFS (2.0.4) and both btrfs and xfs locked up the system. Something to do with the loopback mount. Too bad I could not use the folder mapping and I always got an error that Docker service could not be started. I moved the docker.img to my cache drive and I don’t care too much since it’s disposable. I think I will make latest zfs the default for the next upgrade to unRaid and add a disclaimer that you cannot save the docker.img on ZFS if the problem will still be present. Sent from my iPhone using Ta

Just set up automatic snapshots using something like Sanoid on the running vms. https://forums.unraid.net/topic/94549-sanoidsyncoid-zfs-snapshots-and-replication/ Of course it’s always better to turn off the VM if you are doing something like a migration. Sent from my iPhone using Tapatalk

I was trying this on my server, but the Docker service would not start when I pointed the Docker data-root to a folder on ZFS. Worked fine using folders on Btrfs/Xfs formatted drives.

Builds for 6.9.2 have been added (2.0.0 and 2.0.4 if you have enabled "unstable" builds) Thanks to @ich777 the process is now automated! When a new unRAID version is released ZFS is built and uploaded automatically. Thanks a lot to @ich777 for this awesome addition!

Check this out. I love it for snapshots and replication https://forums.unraid.net/topic/94549-sanoidsyncoid-zfs-snapshots-and-replication/

There are packages going back to 6.1.2 so 6.8.1 is definitely supported. Are you maybe on an old beta or RC? In any case I would just update to 6.9 just for fun I installed 6.8.1 and it worked

Awesome, great to hear Here are the relevant parts from the docker setup, but take note that I have not updated to check_mk 2.0 - a good weekend project for me checkmk/check-mk-raw:1.6.0-latest https://hub.docker.com/r/checkmk/check-mk-raw https://checkmk.com/application/files/2715/9834/3872/checkmk_icon_neg_v2.png http://[IP]:[PORT:5000]/cmk/check_mk/ --ulimit nofile=1024 --tmpfs /opt/omd/sites/cmk/tmp:uid=1000,gid=1000

Added a build of ZFS 2.0.4 for 6.9.1 for those who are using unstable

You won't get spindown with zfs. It's a striped filesystem and you have to read/write from all the disks at once Sent from my iPhone using Tapatalk

Yes it's still the same Sent from my iPhone using Tapatalk

Added ZFS 2.0.0 for unRAID 6.9.1. Also 2.0.3 in the "Unstable" folder you can manually enable

Did you try the new bind-mount to a directory that was added? In any case I moved 2.0.3 to unstable and added a 2.0.0. build instead (thanks ich777) You can move to 2.0.0. by deleting the 2.0.3 package and reboot: rm /boot/config/plugins/unRAID6-ZFS/packages/*

Added ZFS v2.0.0 build for 6.9.0 stable (2.0.3 in the unstable folder) Added ZFS v2.0.3 build for 6.9.0 stable This hopefully fixes the problems with docker.img and zfs 2.0.1+ : ".. we added the ability to bind-mount a directory instead of using a loopback. If file name does not end with .img then code assumes this is the name of directory (presumably on a share) which is bind-mounted onto /var/lib/docker. For example, if /mnt/user/system/docker/docker then we first create, if necessary the directory /mnt/user/system/docker/docker. If this path is on a user share we then "de-ref

Done. You can still use it by enabling unstable builds Sent from my iPhone using Tapatalk

ZFS v2.0.3 built for Unraid 6.9.0-rc2 (Kernel v5.10.1) It is in the main folder so be adviced if there are still problems with having docker.img on zfs: