Cache Drive Full

[ldog88]

Hi,

My I've just noticed my server has shut down all the dockers as I wasnt able to access them remotely.

When logging in I had an array of errors and the cache drive is full.

I have not made any changes on the server for a while so not sure what has caused this.

Is anyone able to point me in the right direction?

Thanks

diagnostics-20230425-2130.zip

[itimpi]

It looks as if your docket.img has been corrupted due to the cache getting completely full.    BTRFS systems are prone to corruption if they run out of free space.  You should set a Minimum Free Space on your pools to set the point when they should start overflowing to the array rather than continue filling up the cache drive and causing problems.

 

Once some space is available on the cache pool you should recreate your docker image file as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

[ldog88]

Hi, thanks for your response. 

I don't know why the cache drive is suddenly full. Is there a way of viewing which files are large that have filled the space without going into each folder manually? 

Hopefully I can locate a large file and just delete it to create space? 

Thanks 

[trurl]

You can see how much of each disk is used by each user share by clicking Compute... for the share on the User Shares page, or the Compute All button at bottom.

 

Except for the "prefer" shares which should stay on cache, this is the only share with files on cache in those diagnostics, and just running mover should get them off unless they are open or duplicates.

b-----s                           shareUseCache="yes"     Exists on cache, disk1

Since you have such a small "cache", you might consider switching that share to use the "cache-downloads" pool after you get it moved from the "cache" pool.

 

You might also consider a smaller docker.img when you recreate it. 20G is often more than enough