Visua

Sadly it turns out Unraid overrides the root compression setting for the pools on starting the array, and it defaulted to off for both my pools. Of course I can enable compression in the GUI after stopping the pool again, but I had one of them set to zstd-2 which isn't even an option in Unraid. (Why???) Dataset local compression settings are kept as is thankfully, but for almost all my datasets I relied on inheriting it from the pool. Easy enough to set it for each dataset, just a bit annoying that Unraid needlessly messes with this. Thankfully the only real issue I encountered is with my docker image. Being contained in a zvol on a pool it has to be mounted after the pool is started, which worked fine, but then Unraid cannot stop the array until I manually unmount that zvol. I'll switch to directories as recommended in https://docs.unraid.net/unraid-os/release-notes/6.12.0/#docker and just live with the horrible dataset pollution it causes. Seeing all the root directories on my pools listed as user shares (with primary storage: array) makes me a bit nervous, but I suppose that won't affect anything especially if I never access anything through /mnt/user?

Thanks for the detailed answer, that really put my mind at ease. Since 6.12.6 includes a version of ZFS that fixes the scary silent corruption bug I guess I will try and update soon.

I'm sure you guys must be tired of these posts, but I'm still unsure about how to migrate from 6.11.5 with this plugin to 6.12. Here's everything about my setup related to ZFS that I think might be affected in some way: The classic setup of an unused USB stick for the array + Unassigned Devices for drives that are part of my ZFS pools. 2 ZFS pools (with 6.12-compatible names thankfully). Autotrim is enabled on 1 pool. Compression is set to lz4 on 1 pool and to zstd-2 on the other. Scripts to scrub and check pool health scheduled through the User Scripts plugin. Docker image is inside a zvol on one of the pools (as a workaround for the major docker+ZFS issue caused by 6.11 or whatever it was). Shares on the pools are setup through smb-extras.conf. My go file has some ZFS related lines: mount /dev/ssd/dockerzvol-part1 /mnt/ssd/dockerzvol echo 0 > /sys/module/zfs/parameters/zfs_dmu_offset_next_sync This has always worked perfectly (except for that time docker broke), and I'd like to keep things running the way I'm used to. Looking at the 6.12 release notes I see the instructions on how to import pools created with this plugin, but it's still unclear to me what exactly the result of importing the pools into Unraid will be. I don't want them to become part of the array in any way and I don't care about a GUI. I just want to them mounted and accessible the way they are now. It says "Compression can be configured as on or off, where on selects lz4. Future update will permit specifying other algorithms/levels.". Will this cause any issues for my zstd-2 pool / datasets? There is a lot about changes to shares and mentions of ZFS, but can I ignore all this and just keep using my smb-extras.conf? Is there anything else I should be mindful of? Thanks in advance.