It appears that if the Minimum Free Space value for a share is larger than the Minimum Free Space value for a pool then the Share value takes precedence when deciding whether to place new files on the cache/pool or directly to the array. I would have thought these settings should be independent? If you have set a largish value on the share to avoid array disks getting very full this behaviour can lead to the cache/pool often unexpectedly not being used even when the free space on the cache/pool is well above the minimum free space setting for the cache/pool.
If it IS desired behaviour then at the very least the GUI Help text for this setting on a cache/pool should be updated to mention this.
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.