Hi everybody,

I have a question regarding shares with caches as primary storage and array as secondary.

My current setup is as follows:

I habe one cache of 1TB

and one array of 15TB (7TB free).

I have multiple shares (appdata, appstorage) all with the same settings.

Primary storage: cache

Secondary storage: array

"Move-Action": Array -> Cache

Minimum free space is 20GB for each share.

I thought, when an app writes data to appstorage and the cache becomes full, the app writes data to the array automatically.

In my case the app tries to write to cache until its full and crashes after that.

Is this the right behaviour or maybe I have a wrong setting somewhere?

Thank you in advance

Greetings

Once it hits the share floor, it should write to the array, assuming it's writing to /mnt/user/share, /mnt/cache/share won't overflow.

Thank you for your reply.
What do you mean by "share floor"? So my understanding was right?
What could cause my overflow of the cache? Do I need to have been below the limit first before it works?

My Idea would be, stop all Docker. Move all cache data to the array via mover. Recreate the cache and then move the data back to the cache again. I would like to have as much "active" data in the Cache as possible, to reduce spin up of some HDDs.

10 minutes ago, klaushipp said:

What could cause my overflow of the cache? Do I need to have been below the limit first before it works?

Not quite sure what you mean? You need to be below the limit specified at the point a new file is first created before overflow starts happening.

Sorry, for being a little bit unclear. The cache had 10GB left. The limit at that point was 5GB I think. I increased the limit to 18GB. So the cache was above limit at that point.

If the floor was set to 18GB and the pool had 10GB free, any new writes should go to secondary. Note that any modified or overwritten files would still go to primary.