BasWeg

So, what's about the other .img files, used for VMs and so on? Are there any issues? I'm still at RC1 with zfs-2.0.0-1

All this samba staff is pretty well explained in this referenced topic https://forum.level1techs.com/t/zfs-on-unraid-lets-do-it-bonus-shadowcopy-setup-guide-project/148764

So, at the moment it is better not to update? I'm still on RC1 with ZFS 2.0.0

So, use_unstable_build is not needed any more to get version 2.0.0?

Thanks for the hint! I've made a user script with following content in order to run after first array start: #!/bin/bash #from testdasi (https://forums.unraid.net/topic/41333-zfs-plugin-for-unraid/?do=findComment&comment=875342) #echo "[pool]/[filesystem] /mnt/[pool]/[filesystem] zfs rw,default 0 0" >> /etc/mtab #just dump everything in for n in $(zfs list -H -o name) do echo "$n /mnt/$n zfs rw,default 0 0" >> /etc/mtab done

Is it possible to get rid of / waiver this error/warning? I know that I'm using an unstable version, and everytime after a reboot this shows up and shocks me. 🙃

Is a reboot required to get the new update, or is the other way - delete and reinstall the plug-in - still working?

After one small issue, zfs-2.0.0-rc6 & unRAID-6.9.0-beta35 is working now. Thanks

Hi @steini84, at the moment I'm using zfs-2.0.0-rc5 for 6.9.0-beta30 and want to update to zfs-2.0.0-rc6 & unRAID-6.9.0-beta35. Just to be sure... maybe you have some additional hints... first update to beta35 -> with or without reboot? With reboot, the zfs pool won't be available afterwards, or? So, I guess no reboot. update the plugin (do I need to touch /boot/config/plugins/unRAID6-ZFS/USE_UNSTABLE_BUILDS again?) reboot keep fingers crossed during reboot... best regards

Not really, I can add the additional path on my own. EDIT: Maybe it is not needed if the /tmp location stores that cache and sidecar stuff. I want to have the photoprism docker configuration/settings in one zfs folder with snapshots and the generated cache stuff in an other folder (with no snapshot) But please remove the trailing spaces at the two key names for database configuration.

Please also for the cache directory if possible. thank you

I‘ve seen this filling up, too. ~300GB data in cache due to indexing of ~160k pictures. you can change the cache path with a docker variable. https://docs.photoprism.org/getting-started/caching/ I will check this as soon as possible, too.

Hi, I've just tried to usw mysql for photoprism. I've created a mysql user "photoprism" and database "photoprism" in advance, but photoprism itself does not use the mysql database (no table is created), instead the index.db file is growing. I'm using following flags: -e 'PHOTOPRISM_DATABASE_DRIVER '='mysql' -e 'PHOTOPRISM_DATABASE_DSN '='photoprism:photoprism_pwd@tcp(192.168.xx.xx:3306)/photoprism?charset=utf8mb4,utf8&parseTime=true' After a fresh start there is no information regarding the database used: time="2020-10-30T12:36:36+01:00" level=info msg="webdav: /originals/ waiting for connection" time="2020-10-30T12:36:36+01:00" level=info msg="webdav: /import/ waiting for connection" time="2020-10-30T12:36:36+01:00" level=info msg="starting web server at 0.0.0.0:2342" time="2020-10-30T12:36:42+01:00" level=info msg="session: open /photoprism/storage/cache/sessions.json: no such file or directory" Do you have any suggestions? EDIT: SOLVED... during posting this comment, I've seen that the keys PHOTOPRISM_DATABASE_DRIVER and PHOTOPRISM_DATABASE_DSN had an extra ' ' (space character) in the template. I've removed this in the edit-dialog, now the database-tables are created 😅 Thanks and best regards Bastian

Which mountpoints do you have/use for your zfs pools?

Ok, I had the same issue like you. Stopping a VM crashed libvirt and a restart was not possible. I‘ve solved this with xattr=sa for the VM datasets, but good to know that this issue is resolved with RC4 now.

A lot of bugfixes/improvements: https://github.com/openzfs/zfs/releases I believe in RC4 is even the bugfix that could resolve Marshalleq issue (https://github.com/openzfs/zfs/pull/11025)

😅 no problem

Hi, I've tried the update by removing the plugin (via gui) and installed it again. It's mentioned that RC4 is included, but even after reboot RC3 is still active. Oct 21 19:17:40 UnraidServer root: Remounting modules Oct 21 19:17:40 UnraidServer root: Oct 21 19:17:40 UnraidServer root: Verifying package zfs-2.0.0-rc4-unRAID-6.9.0-beta30.x86_64.tgz. Oct 21 19:17:41 UnraidServer root: Installing package zfs-2.0.0-rc4-unRAID-6.9.0-beta30.x86_64.tgz: Oct 21 19:17:41 UnraidServer root: PACKAGE DESCRIPTION: Oct 21 19:17:42 UnraidServer root: Executing install script for zfs-2.0.0-rc4-unRAID-6.9.0-beta30.x86_64.tgz. Oct 21 19:17:42 UnraidServer root: Package zfs-2.0.0-rc4-unRAID-6.9.0-beta30.x86_64.tgz installed. Oct 21 19:17:42 UnraidServer root: Oct 21 19:17:42 UnraidServer root: Deleting old files.. Oct 21 19:17:42 UnraidServer root: Oct 21 19:17:42 UnraidServer root: Loading ZFS modules and importing pools (this could take some time) Oct 21 19:17:42 UnraidServer root: Oct 21 19:17:43 UnraidServer ntpd[1966]: receive: Unexpected origin timestamp 0xe33aebb7.120d9f40 does not match aorg 0000000000.0000000 0 from [email protected] xmt 0xe33aebb7.816ccfb4 Oct 21 19:17:43 UnraidServer kernel: znvpair: module license 'CDDL' taints kernel. Oct 21 19:17:43 UnraidServer kernel: Disabling lock debugging due to kernel taint Oct 21 19:17:45 UnraidServer kernel: ZFS: Loaded module v2.0.0-rc3, ZFS pool version 5000, ZFS filesystem version 5 Oct 21 19:17:51 UnraidServer root: plugin: unRAID6-ZFS.plg installed Oct 21 19:17:51 UnraidServer root: plugin: installing: /boot/config/plugins/unRAID6-ZnapZend.plg Any idea? best regards Bastian

Hi, I'm new with unraid and just startet with ZFS for Docker/Vms (SSDs) and ZFS for data like pictures. I had the roughly same issues, that after closing a VM the kernel throws a panic, and afterwards a restart of the VM was not possible. (libvrt stucks). Yesterday, I've destroyed the datasets for my ubuntu and MacOs VMs and created new ones with the xattr=sa. (zfs set xattr=sa <dataset>). Afterwards I've installed both VMs new and until now everything is working fine. I guess that there are maybe some permisson issues regarding the lock files and attributes. With xattr=sa these are not handled in the filesystem anymore. Maybe I'm wrong, but nevertheless, even after some reboots of UNRAID the VMs issue is gone. best regards Bastian