steini84

This should bring some attention to ZFS on unRAID. Fun to see the plugin being used here

The thing is that we are not making any changes just shipping ZFS 2.1 by default. We have shipped 2.0 by default until now because of this deadlock problem, and 2.1 if you enabled "unstable builds" (see the first post). ZFS 2.0 only supports kernels 3.10 - 5.10, but unRAID 6.10 will ship with (at least) kernel 5.13.8 therefore we have to upgrade to ZFS 2.1 So if you are running ZFS 2.1 now on 6.9.2 or 6.10.0-rc1 there wont be any changes: You can check what version is running i two ways: root@Tower:~# dmesg | grep -i zfs [ 69.055201] ZFS: Loaded module v2.1.0-1, ZFS pool version 5000, ZFS filesystem version 5 [ 70.692637] WARNING: ignoring tunable zfs_arc_max (using 2067378176 instead) root@Tower:~# cat /sys/module/zfs/version 2.1.0-1

Great video: Sent from my iPhone using Tapatalk

The plugin update helper does not add itself in the apps tab. When you install/upgrade the ZFS plugin the update helper is bundled with and watches for upgrades to unRAID. Good question, i personally just changed to location and rebuilt my docker.img, but you could also disable docker, move the file, change the location and then enable docker again. Just be sure to have the Community apps plugin installed so you can easily go to Apps->"previous apps" and re-install all your dockers, while keeping your settings:

The plugin has been updated with the "Plugin Update Helper" from @ich777 It basically sanity checks and pre-grabs the needed files for ZFS when you are updating unRAID. If there would be any problems the plugin would let you know so you dont reboot and lose ZFS support. This with the automatic builds from @ich777 I think ZFS on unRAID is as good as it gets before, we get native support. Heads up for using ZFS with Docker. Starting with unRAID 6.10.0 we are shipping ZFS 2.1 which has a issue for some users with storing docker.img on a ZFS pool. This does not affect the appdata, but only the docker.img file. I recommend storing docker.img on your cache disk if you run into any problems, as it does not contain any critical information and can be easily recreated.

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 Tapatalk

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-reference" the path to get the disk path which is then bind-mounted onto /var/lib/docker. For example, if /mnt/user/system/docker/docker is on "disk1", then we would bind-mount /mnt/disk1/system/docker/docker. " Sent from my iPhone using Tapatalk

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:

I have uploaded a zfs 2.0.2 build for 6.9.0-rc2 but since there have been some reports of errors with the 2.0.1 builds I put it in the unstable folder. @Marshalleq maybe you can let us know if the problem has been fixed in 2.0.2?

Yeah this should do the trick: znapzend --debug --logto=/var/log/znapzend.log --daemonize I also want to let you know that I was using znapsend and ran in to some problems, for example after changing datasets. I moved over to Sanoid/Syncoid and have not had a single problem since. Not saying that one solution is better than the other, but that was my experience and I would reccomend that you check it out

Its done, thanks

I have moved the 2.0.1 builds to the unstable folder for now. #Enable unstable builds touch /boot/config/plugins/unRAID6-ZFS/USE_UNSTABLE_BUILDS rm /boot/config/plugins/unRAID6-ZFS/packages/* #Then reboot #Disable unstable builds rm /boot/config/plugins/unRAID6-ZFS/USE_UNSTABLE_BUILDS rm /boot/config/plugins/unRAID6-ZFS/packages/* #Then reboot Please let us know if you are running 2.0.1 without issues and better yet if the conflict reported by Marshalleq has been identified / resolved

You can use smb-extras.conf[emoji108] Sent from my iPhone using Tapatalk