There have been a couple of reports of minimum free space not being respected with v6.10, I found a circumstance where it's easily reproducible, there might be others.
To reproduce:
-create a new share, set allocation method to fill-up, don't set minimum space for now, click apply
-now set minimum space, click apply again
-to test with SMB enable share export, or test locally
-now copy something to that share and minimum free space won't be respected, it will fill up the disk until ENOSPC
-stop/start the array will make the setting start to work correctly.
This doesn't happen with v6.9.2.
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.