Hello, i'm having this issue with docker container giving the error message: SQLite Error 6: 'database table is locked'. whenever the cache drive gets full, however i'm a bit confused on how things work i have on my data share the primary storage set to my cache then the secondary storage to my array; once the cache drive gets full isn't it supposed to use the secondary storage? why such an error happens? and what can i do to fix it?

after running a mover the error goes away btw so i know that is indeed the problem since i've been having it for a week straight.

 

 

unraid-diagnostics-20240525-2214.zip

Edited May 25, 20242 yr by giovacca

Attach Diagnostics to your NEXT post in this thread. 

 

42 minutes ago, trurl said:

Attach Diagnostics to your NEXT post in this thread. 

done as soon you replied, had forgot that

unraid-diagnostics-20240525-2214.zip

Edited May 25, 20242 yr by giovacca

Go to   SETTINGS    >>>>   Scheduler   and look for the section called   Mover settings   

 

Make sure that you have set it up.   You should probably click on the 'Move now' button.   

7 hours ago, Frank1940 said:

Go to   SETTINGS    >>>>   Scheduler   and look for the section called   Mover settings   

 

Make sure that you have set it up.   You should probably click on the 'Move now' button.   

i have set that to run once every hour, doesn't seem to be working tho but that still doesn't answer my question 

Edited May 26, 20242 yr by giovacca

  

11 hours ago, giovacca said:

once the cache drive gets full isn't it supposed to use the secondary storage? why such an error happens? and what can i do to fix it?

It will start overflowing NEW files to the array once the free space on the pool falls below the value you have set for Minimum Free Space for the pool.   Existing files that are growing are never moved so you have to allow for that in the pool's Minimum Free Space setting.

 

You need to set an appropriate value for Minimum Free Space for the 'media' pool.

14 hours ago, giovacca said:

 

This drive is full! 

 

You should probably install the Dynamix File Manager plugin and see what is being stored there.  (The 'Calculate' button will tell you how much is stored in each directory...)

5 hours ago, giovacca said:

i have set that to run once every hour,

 

If you are putting that much data onto your server that you can significantly fill a 1TB drive in an hour, you really should NOT be using caching uploads.   Write directly to the array. 

 

If you go to   SETTINGS   >>>   Disk Settings    and look at the 'Disk Settings' section for the parameter shown below

and set it as shown, you will significantly increase the write speed directly to the array.

Edited May 26, 20242 yr by Frank1940

1 hour ago, Frank1940 said:

 

If you are putting that much data onto your server that you can significantly fill a 1TB drive in an hour, you really should NOT be using caching uploads.   Write directly to the array. 

 

If you go to   SETTINGS   >>>   Disk Settings    and look at the 'Disk Settings' section for the parameter shown below

and set it as shown, you will significantly increase the write speed directly to the array.

just found out why it wasn't working, was using a plugin called mover settings or something like that and it completely broke the mover, now it works fine. and thanks for the tip on the setting, it was already set to that on my unraid

According to those earlier diagnostics, your appdata and system shares have files on the array.

 

Ideally, appdata, domains, and system shares would have all files on cache or other fast pool with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

 

Also, why do you have 500G docker.img? Have you had problems filling it? The usual cause of filling docker.img is an application writing to a path that isn't mapped.

 

Your docker.img was only using 18G in those diagnostics. Probaby 30G would be more than enough. And it should be on a fast pool with the rest of the system share.