[Solved] No space left on device even after adding new drive

I just added a new drive, made sure it's formatted and recognized, the mover successfully moved files from the cache SSD onto the new HDD after this, which freed up space on the cache, which was getting full due to all of my HDDs being full.

But my shares are still throwing "No space left on device" when some applications try to write to them, even though, the minimum free space on the shares is set to 50 GB or less for every share and the free space is more than this. It doesn't seem to matter if the primary storage is cache or array. Shares with either setting have been throwing the error. The cache currently has 1.39 TB free and the new drive has 16.1 TB free. Which is obviously way more than the minimum free space setting is set to.

The issue currently is occurring in a VM where most of my server stuff is running. I have a few dockers and I have not noticed any issues with them, but they generally don't write much to shares. This was previously working fine right up to the new HDD install & Unraid update, as I've been periodically deleting some files to free up space and was not having any issues creating new files after freeing up space.

At the same time I installed the new drive (just a couple days ago), I also updated Unraid to the latest since it was a good opportunity to update. Is there some regression in the latest version?

I will add that I've rebooted both the VM and Unraid in the hopes that maybe it just needed a reboot after the new drive was added to the array for software to recognize it properly.

Here is an example of a problematic share. Most of my shares use similar settings though a couple are set to cache only or array only.

And, as you can see, the dashboard shows the correct free space. Although, why the first drive is filled to the brim and still seems to be constantly being written to, I am not sure.

Edit: I am thinking that maybe whatever is being written to happens to be on that first disk, which is just too full for the existing file to expand. As I seem to be able to create new files fine.

Edit2: It seems like that was it. I had to manually move some files from disk1 to disk5, and after that the error from before seems to be gone.

I wish that unRAID was smart enough to relocate the file if it needs to expand beyond available free space but there is enough space on another disk, as this could happen again in the future. Setting the minimum free space to a larger amount than the largest file size you expect to ever encounter is not really a good solution, since the future is unpredictable, and it also leaves that amount of space unusable on every single drive which is a significant amount of unusable space.

Edited July 4, 20251 yr by Jdbye