steini84

Community Developer
  • Content Count

    402
  • Joined

  • Last visited

Everything posted by steini84

  1. I would like to hear if someone knows the answer to this. This has happened to me using a USB disk (power failure, disconnected etc.). On Linux (unRAID and Debian) the server works fine, but I get incredibly high load and nothing I try works to reset ZFS to a useful state. I could not even reboot normally and had to force a reboot. In FreeBSD this is similar, but since the load is calculated differently there the signs were not as obvious, but pretty much the same problem.
  2. Yes excactly. The master branch is still using version number 0.8.0 and only the releases get a updated version number. Sent from my iPhone using Tapatalk
  3. Ok let me try to make it clear I just updated the plugin to 1.0 since new builds are not dependant on an update to the plugin. On boot the plugin checks for available builds and installs the latest one available for Unraid The latest build for Unraid 6.8.3 is OpenZFS 0.8.4 and I usually only build from the releases (see them @ https://zfsonlinux.org/) Since Unraid 6.9 beta 22 is running on Kernel 5.7, which is not supported in OpenZFS 0.8.4, I made a build from the latest master (commit 2e6af52). I hoped that some changes were already in the master branch
  4. Built ZFS from the latest master for 6.9.0-beta22. You can re-install the plugin to try it out. I would not trust it for anything important, but then again you should probably not be running the beta version of Unraid on your production server
  5. Linux 5.7 is not yet supported https://github.com/openzfs/zfs/releases/tag/zfs-0.8.4 I have not tried to build it because of that, but I’ll start a build now and see what happens. But a great quote from the release notes from the 9.3 beta “We are also considering zfs support.” Sent from my iPhone using Tapatalk
  6. I have updated to the 0.8.4 release. Persistent l2arc has been added to the master branch, but it has not made it to a release yet. It appears that it will be included in the 2.0 release - "The features in progress or ported for OpenZFS 2.0 is lengthy, and includes:" ref: https://en.wikipedia.org/wiki/OpenZFS You can follow the changelog over @ https://zfsonlinux.org/
  7. It should be included since 0.7 https://openzfs.org/wiki/ZFS_Hardware_Acceleration_with_QAT Sent from my iPhone using Tapatalk
  8. To Each Their Own, but if you read the first post you can understand why this plugin exists and what role zfs plays in a unRAID setup in my mind. If I wanted to go full on zfs I would use Freenas/Ubuntu/Freebsd/Omnos+napp-it but I think zfs for critical data and xfs with parity data for media is just perfect and have been running a stable setup líka that since 2015 [emoji123] Sent from my iPhone using Tapatalk
  9. It is really easy to run commands when the array starts with this program: You can make it run on array start or even ONLY on the first array start after booting the server. Much easier than using the "go" file. But I cannot answer about the encryption since I´m not familiar enough to give you a good answer 😕
  10. Yeah I saw that interview, hope that they find a creative way to integrate ZFS [emoji3060] Sent from my iPhone using Tapatalk
  11. Wow that is great. I try my best to update ASAP but it’s awesome that we are getting more ways to enjoy ZFS. Hope it will one day be native in unraid, but until then it’s great to see more options [emoji2] Sent from my iPhone using Tapatalk
  12. Here you go - have fun and don't break anything https://www.dropbox.com/s/dvmgw6iab43qpq9/zfs-0.8.4-draid-feature-unRAID-6.8.3.x86_64.tgz?dl=0 https://www.dropbox.com/s/rrjpqo0zyddgqmn/zfs-0.8.4-draid-feature-unRAID-6.8.3.x86_64.tgz.md5?dl=0 To install this test build you first have to have the plugin install, then fetch the .tgz file and install it with this command: installpkg zfs-0.8.4-draid-feature-unRAID-6.8.3.x86_64 If you want to to persist after reboot you have to fetch both files, rename them to: "zfs-0.8.3-unRAID-6.8.3.x86_64.tgz & zfs-0.8.3-unRAID-6
  13. Built ZFS 0.8.4 for unRAID 6.8.3 & 6.9.0-beta1 (kernel 5.5/5.6 officially supported in this ZFS version) The upgrade is done when you reboot your server Changelog can be found here: https://github.com/openzfs/zfs/releases/tag/zfs-0.8.4
  14. Have you ran the program and made it auto start on boot? See instruction in the first post of this thread. Sent from my iPhone using Tapatalk
  15. Znapzend runs on an interval, in your case every 2 hours for the 24 hour retention snapshots. You can make it run right away with the command znapzend --runonce=HDD See more @ https://github.com/oetiker/znapzend/blob/master/README.md "If you don't want to wait for the scheduler to actually schedule work, you can also force immediate action by calling znapzend --noaction --debug --runonce=src_dataset " Sent from my iPhone using Tapatalk
  16. https://www.dropbox.com/s/zwq418jq6t3ingt/zfs-0.8.3-unRAID-6.8.3.x86_64.tgz?dl=0 https://www.dropbox.com/s/qdkq4c3wqc5698o/zfs-0.8.3-unRAID-6.8.3.x86_64.tgz.md5?dl=0 Just overwrite these files and double check that you actually have to overwrite, the files should have the same name. You have to copy both the files otherwise the md5 check will fail and the plugin will re-download the released binary. Just check after a reboot root@Tower:~# dmesg | grep ZFS [ 4823.737658] ZFS: Loaded module v0.8.0-1, ZFS pool version 5000, ZFS filesystem version 5
  17. Whoops. I assumed you were on unraid 6.9 beta 1 - I will make a build for you for unraid 6.8.3 tomorrow Sent from my iPhone using Tapatalk
  18. I would double check that you overwrote the right file. You should have gotten version v0.8.0-1, (it´s lower I know, but that is the current version give on the master branch @github) you can double check by running these two command and you should get the exact same output root@Tower:~# dmesg | grep -i ZFS [ 30.852570] ZFS: Loaded module v0.8.0-1, ZFS pool version 5000, ZFS filesystem version 5 root@Tower:~# md5sum /boot/config/plugins/unRAID6-ZFS/packages/zfs-0.8.3-unRAID-6.9.0-beta1.x86_64.tgz 8cdee7a7d6060138478a5d4121ac5f96 /boot/config/plugins/unRAID6-ZFS/packages/zfs-0.8.3-unRAID
  19. I built a version for linux 5.5.8 for you from the latest master (https://github.com/openzfs/zfs/tree/7e3df9db128722143734a9459771365ea19c1c40) which includes that fix you refrenced. You can find that build here https://www.dropbox.com/s/i6cuvqnka3y64vs/zfs-0.8.3-unRAID-6.9.0-beta1.x86_64.tgz?dl=0 https://www.dropbox.com/s/6e64mb8j9ynokj8/zfs-0.8.3-unRAID-6.9.0-beta1.x86_64.tgz.md5?dl=0 Copy both these files and replace with the files in /boot/config/plugins/unRAID6-ZFS/packages/ and reboot To verify that you are on the correct build type: dmesg |
  20. It's just openzfs for Linux. Nothing taken out nothing added. For what it's worth I have ran the same zfs pool on unraid since 2015 without any problems. Zfs send and recv work fine Sent from my iPhone using Tapatalk
  21. It's just openzfs for Linux. Nothing taken out nothing added. For what it's worth I have ran the same zfs pool on unraid since 2015 without any problems. Sent from my iPhone using Tapatalk
  22. I have heard some discussion about it, but to be honest I do not run the 6.9 beta with kernel 5.5x so I have not ran in to any issues. I am on stable 6.8.3 with kernel 4.19.107 which is running fine with ZOL 0.8.3 You can watch the progress of openzfs here https://github.com/openzfs/zfs
  23. I don't think that is possible because you have to have "from" and "to" snapshots to compare the difference, but I recommend that you go over to https://www.znapzend.org/ and check the "get help" section
  24. No I accidentally pushed a broken update , but it’s correct now Sent from my iPhone using Tapatalk