Hi,

 

I have notices that when minimim free space for a share is larger than free space on chache drive UNRAID refuses to use the chache drive ang give you error message "UNRAID shfs: share cache full" in the log no matter what size the file you try to copy is.

My three array drive are 10TB each and I have set minimum free space to 300GB which I think is pretty low for 10TB drives, then I have a 120GB chache drive that have about 95GB free, which means will never be used due to this. 

 

Is there any way to get around this other than lower the minimum free space or get a larger chache drive?

Edited December 9, 20196 yr by gberg

This is normal and expected behavior, any reason you need 300GB free on the array disks? Minimum free space is usually set to a little over the largest file you expect to copy that share.

Maybe I'm too used to use Windows where you shouldn't fill drives too much, minmimum 15% free space is a common number.

So You say it's no problem to fill it pretty much to 100%, if I for instance set minimum free space to 50GB which is 0,5% free space, it's still OK?

7 minutes ago, gberg said:

if I for instance set minimum free space to 50GB which is 0,5% free space, it's still OK?

More than OK, as long as you leave 15 to 30GB in each drive for any filesystem repair needed you won't have any issues.

Ok, then I wonder why the Default warning/critical disk utilization threshold is set to 70/90%, wouldn't it be better if that was set in absolute numbers too?

That's been discussed before, don't remember the reasoning but it's how it is currently, I have most of my disks set to 99/100 for warning/critical

ok, thanks for the info.