Hi, I have an issue, that my cache drive "single_cache" is marked as full alsough ther is plenty of space. Fix Common Problems and "More Information" told me to place this request. I alredy tried some things I found in the net but nothing worked. Can you give me a hint?

 

Plan B would be to empty the drive and completely renew it.

 

Thanks!

unraid-diagnostics-20240205-2006.zip

The drive is clearly not full, likely whatever share you're trying to write to has an improperly set "min free space".

Hi, that was also my idea, but I reduced "Minimum free space" in the Shares Section for all oft the shares to a minimum (I tried 1 GB, 1 MB etc.) and it doesnt make any difference, which share I'm using, it's currently 157 GB free space and writes to the drive stopped when I tried to copy, starting from 6XX GB fre space. SMB still tells me, that ther is free space.

So where do I have another setting to reduce "min free space"? Could it be a bug and I have to change it in the config files?

 

Btw. Also in "Main" and the Drive Settings, minimum free space is "0"

Edited February 6, 20242 yr by ikarus82

The filesystem is completely allocated, see here:

 

https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551

 

Thank you, but: You do not have permission to view this topic.

Strange, I'll copy/paste here:

 

you need to balance your cache:

 

btrfs balance start -dusage=75 /mnt/cache

If you get ENOSPC lower the 75 until you can complete a balance, e.g. try -dusage=50, 25 and so on, then do again with an higher number until you can do with at least 75.

Thank you, but after making the drive empty, there were still about 370 GB of used space. SO I formated it after saving an now I will have a look what happens if I use it again.

 

btrfs balance start -dusage=75 /mnt/cache

was without any error before.

A new filesystem created with current kernel should no longer run into that issue, at least not as frequently, but it still may happen is some cases.