This was originally reported here and seemed to be fixed at some point meaning the cache drive could be fully utilized.
However, when I upgraded to 6.10.x the issue/bug seems to be occurring again.
I have my shares set to leave 500gb free on all my array drives, however this means that when my 1tb cache drive gets to 500gb utilization, any new copies start to write to the array, The old functionality used fill up the cache drive to 1tb and then start to write to the array.
I cant see how this could have been implemented as a design feature by the fact that the functionality keeps changing and it also makes having large cache drives completely redundant if it only uses some of the available space.
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.