steini84

Community Developer
  • Content Count

    400
  • Joined

  • Last visited

Community Reputation

84 Good

3 Followers

About steini84

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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!
  3. Check this out. I love it for snapshots and replication https://forums.unraid.net/topic/94549-sanoidsyncoid-zfs-snapshots-and-replication/
  4. 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
  5. 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
  6. Added a build of ZFS 2.0.4 for 6.9.1 for those who are using unstable
  7. 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
  8. Yes it's still the same Sent from my iPhone using Tapatalk
  9. Added ZFS 2.0.0 for unRAID 6.9.1. Also 2.0.3 in the "Unstable" folder you can manually enable
  10. 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/*
  11. 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
  12. Done. You can still use it by enabling unstable builds Sent from my iPhone using Tapatalk
  13. 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:
  14. 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?
  15. 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