Fix common problems has told me that I am at 64% full, my server has only been running for 13 days. I'm completely clueless, can anyone help me with this? 

tower-diagnostics-20190515-1245.zip

Settings - Schedules - Mover Settings, disable mover logging.

 

You might also be a little too aggressive on the auto turbo mode settings, as it's enabling / disabling every 15 minutes (each of which results in 2 logged lines)

Mover logging was already disabled.

 

I have disks allowed to be spun down before invoking turbo mode set to 2 and I changed the polling time from 300 to 3600 seconds. 

Additional debugging logging was set to no already and I left it at no. 

 

Would that be all that is causing it? 

 

I think you must be writing something to /var/log besides syslog. Do you have atop installed?

 

 

No, would that tell me what's being written? 

 

No, atop (in Nerd Pack) is a frequent culprit of filling /var/log.

 

What do you get from the command line with this?

du -h /var/log

 

I do have it on in nerdpack, I must have enabled it while following a spaceinvader video. 

Or better, this command

du -sh /var/log/*

 

I don't see anything there. Did you reboot or something? Are you still having the problem?

 

What do you get with this command?

df -h

 

Sorry, I thought I had given all the info I would need so I updated to 6.7.0. It's been up for almost 2 days now. 

And of course, that shows you aren't currently having the issue.

ok it has now been running for 10 days and I have the error again 

tower-diagnostics-20190601-1325.zip

On 5/16/2019 at 9:44 AM, trurl said:

Or better, this command

du -sh /var/log/*

 

 

Not related but your system share has files not on cache and your docker image is much larger than recommended.

4 minutes ago, trurl said:

Not related but your system share has files not on cache and your docker image is much larger than recommended.

That's weird, system is set to prefer cache and mover is set to every 4 hours. 

atop is the culprit. Why do you have that installed?

 

Looks like we already discussed this very thing in this thread. Why do you have atop installed? I suggest not installing anything in Nerd Pack unless you know you need it.

 

 

ok, it was installed so I could see cpu usage in the bottom right of the screen, but having a clear fix common problems screen is better for me. 

12 minutes ago, darthjonathan12 said:

That's weird, system is set to prefer cache and mover is set to every 4 hours. 

Mover can't move any open files.

 

Go to Settings - VM Manager and disable.

 

Go to Settings - Dockers and delete and recreate your docker image at the much more reasonable size of 20G.

 

Run mover manually. After it completes you can check which disks each user share is using by going to User Shares and clicking Compute... or Compute All button.

 

If your system share is all on cache now you can reinstall all your dockers just as they were by using the Previous Apps feature on the Apps page.

 

Not related, but why do you think you need to run mover so often? It is best to have mover running at a time when it won't need to compete with other processes for access to the disks.

 

5 minutes ago, darthjonathan12 said:

ok, it was installed so I could see cpu usage in the bottom right of the screen, but having a clear fix common problems screen is better for me. 

I don't use atop but if you want to use atop then you should take it upon yourself to learn how to manage it so it doesn't fill up your log space.