tower-diagnostics-20230521-1435.zip
I’ve been running 12.RC5 and now 12.RC6 as upgraded from 11.5 and I’m experiencing a problem with Mover. For 11.5 I had been running a dedicated mover_cache using a single SSD formatted as XFS. With the move to 12.RC5 I decided to reformat the mover_cache as ZFS. I also reformatted my array drives from XFS to ZFS. Now using 12.RC5/12.RC6 when I save a file, such as an Excel Spreadheet, it is appropriately saved on the ZFS formatted pool mover_cache. When I invoke Mover, the file is then moved to the appropriate share on the ZFS Array Drive as it should. No change in behavior from 11.5 using all XFS drives. However if I try to open the file after it has been moved to the Array ZFS drive it is now seen as Read Only. If I open it while it is on the SSD ZFS mover_cache I can open it without issue, full r/w privileges. Things that work most of the time, at least as temporary fixes, are Stop/Start the array, or reformat the mover_cache as ZFS or XFS, or Reboot the server, then the file can be opened with full r/w privileges. Using an XFS SSD mover_cache is a permanent fix, but not relevant. In this configuration, there is no issue but it kind of defeats my hope of mirroring the cache drives in the future.
The only other change I made was to increase the memory available to the ZFS filesystem from 1/8 to ¼. I have 32G of ECC ram and it mostly goes unused so I thought doubling the ZFS ram might be beneficial. Attached is the DIAGNOSTIC immediately after a save that and MOVE resulting in the file being READ ONLY.
My client machine is running MacOS 12.6.5. On Unraid, I have tried toggling the SMB MacOS enhancement, auto trim and compression on the mover_cache and ARRAY but it doesn't seem to matter.
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.