I'm in process of setting up a new system and new to Unraid. I installed using 7.2.0-rc.1 and ran into issues with ultimately three of four new Seagate drives failing in the array. Having not gotten far, I jumped to 7.2.0-rc.2 and with new drives in hand I went the route of a ZFS RaidZ2 pool using 4 discs for my primary storage and deleted the array.

I have several 500G'ish NVME and SSDs around, so I proceeded to use three to create a ZFS RaidZ1 pool for cache.

I have created a couple of shares with the cache as primary and the Z2 pool as the secondary and the mover is scheduled to move files a couple of times a day.

I kicked off a long sync process to backup some cloud storage onto the share and I noticed it's going directly to the Z2 array and not touching the cache. The cache actually "spins" down to inactivity.

Looking at the syslog, I am getting share cache full notices, but the 926GB cache shows 0% utilization.

I installed and ran the Common Problem tool and I'm not sure I'm following what it's saying. If I look at the Cache folder, it's empty and does not have any folders in it and if the destination pool is mars, that it should have files and folders. I expected to find something in the Cache folder which is perplexing.

What am I doing wrong?

Thanks!

 

Oct 18 16:01:09 Unraid emhttpd: shcmd (38626): /usr/local/sbin/mover start &> /dev/null &
Oct 18 16:01:15 Unraid emhttpd: shcmd (38627): /usr/local/sbin/mover start &> /dev/null &
Oct 18 16:01:34 Unraid root: Fix Common Problems Version 2025.08.07
Oct 18 16:01:38 Unraid root: Fix Common Problems: Warning: Share filen set to use pool cache, but files / folders exist on the mars pool
Oct 18 16:01:38 Unraid root: Fix Common Problems: Warning: Share Files set to use pool cache, but files / folders exist on the mars pool
Oct 18 16:01:38 Unraid root: Fix Common Problems: Warning: Share system set to use pool cache, but files / folders exist on the mars pool
Oct 18 16:04:58 Unraid shfs: share cache full
Oct 18 16:04:58 Unraid shfs: share cache full
Oct 18 16:05:16 Unraid shfs: share cache full
Oct 18 16:05:16 Unraid shfs: share cache full
Oct 18 16:05:16 Unraid shfs: share cache full
Oct 18 16:05:16 Unraid shfs: share cache full
Oct 18 16:05:34 Unraid shfs: share cache full
Oct 18 16:05:34 Unraid shfs: share cache full

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

12 hours ago, roadgator said:

Oct 18 16:04:58 Unraid shfs: share cache full

This doesn't mean the pool is full, it means the share you are writing to has a floor set to more than is currently available on the pool, so the new data will overflow to the secondary storage, typically the array, if needed, just adjust the floor setting.

I've got the min free space of the pool set at 5.2GB... roughly 10% of the pool capacity. The default was 0 when I created it, but I did bump it thinking it was the initial issue.

Diagnostics information is attached and I do appreciate the guidance!

I noticed the Common Problem tool indicating an out of memory issue which surprised my, but I believe is unrelated. I have a container running a periodic sync tool and I believe it is leaking ram. The system as about 15GB accessible ram (Integrated Ryzen GPU), and I have the container capped at 4G of ram.

Thanks!

unraid-diagnostics-20251019-0544.zip

You do not mention which share you are talking about, but looking at the diagnostics the likely shares have a Minimum Free Space setting of 1.5TB and the pool does not have this much free space.

Having said that is debatable whether it is worth caching a share that is on a SSD pool in the first place.

59 minutes ago, roadgator said:

I've got the min free space of the pool set at 5.2GB

It's not the pool floor,

1 hour ago, JorgeB said:

it means the share you are writing to has a floor set to more than is currently available on the pool

1 hour ago, itimpi said:

You do not mention which share you are talking about, but looking at the diagnostics the likely shares have a Minimum Free Space setting of 1.5TB and the pool does not have this much free space.

Having said that is debatable whether it is worth caching a share that is on a SSD pool in the first place.

1 hour ago, JorgeB said:

It's not the pool floor,

Thank you both! Now it clicked! Reducing Min Free Space per share is doing the trick.

The Mars pool which is the long term storage is spinners so I was simply trying to move the wear and tear onto the SSD's and let the mars pool spin down.

All is well!