Community Developer
  • Posts

  • Joined

  • Last visited

Everything posted by steini84

  1. Just to put it out there. I have personally moved to sanoid/syncoid Sent from my iPhone using Tapatalk
  2. You can get away with a oneliner in the go file / User Scripts: wget -P /usr/local/sbin/ "" && chmod +x /usr/local/sbin/ioztat But packing this up as a plugin should be a fun project
  3. I want to keep the zfs package as vanilla as possible. It would be a great fit for a plugin Sent from my iPhone using Tapatalk
  4. This is just an unfortunate coincidence, i would guess it´s cabling issues or a dying drive. Have you done a smart test?
  5. You can also keep it under /mnt/cache but don't have it on the flash! Sent from my iPhone using Tapatalk
  6. This not the first time that I've begin to lost control of my unraid server, but until now I didn't lost anything. All I can say, it's begun to appear with the version 2.0 of the plugin, but maybe that it's linked to something else? Are you keeping your docker.img on the zfs array? It can cause the lockup you are describing. Sent from my iPhone using Tapatalk
  7. What I think would make most sense is to have the zfs plug-in as vanilla as possible and extra functionality to a companion plugin. Then the companion plug-in would continue to work when zfs becomes native [emoji41] Sent from my iPhone using Tapatalk
  8. I use check_mk for monitoring and that works perfectly for everything from low space to high load and even failed pools. It takes some time to set up but is really good! A simple bash script can be rigged to check zpool status -x I can set one up when I'm in front of a computer Sent from my iPhone using Tapatalk
  9. You are probably storing docker.img on the zfs pool and running the latest RC of unraid: You can also try to use folders instead of docker.img Sent from my iPhone using Tapatalk
  10. You have truly taken this plugin to the next level and with the automatic builds it´s as good as it gets until we get native ZFS on Unraid!
  11. You can do a pretty basic test using dd dd if=/dev/random of=/mnt/SSD/test.bin bs=1MB count=1024 If you want to test the read speed you change input and output *remember to change to a path within your zfs pool Sent from my iPhone using Tapatalk
  12. Just run this command then reboot rm /boot/config/plugins/unRAID6-ZFS/packages/*
  13. This should bring some attention to ZFS on unRAID. Fun to see the plugin being used here
  14. 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
  15. Great video: Sent from my iPhone using Tapatalk
  16. 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:
  17. 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.
  18. 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
  19. Just set up automatic snapshots using something like Sanoid on the running vms. 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
  20. 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.
  21. 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!
  22. Check this out. I love it for snapshots and replication
  23. 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
  24. 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 http://[IP]:[PORT:5000]/cmk/check_mk/ --ulimit nofile=1024 --tmpfs /opt/omd/sites/cmk/tmp:uid=1000,gid=1000
  25. Added a build of ZFS 2.0.4 for 6.9.1 for those who are using unstable