Contacting my hosting provider fixed the problem. The disk analysis now reads correctly. Unfortunately my host would not disclose the solution or explain what caused the problem. My guess is a disk failure somewhere. Thank you all for your help. Keyhelp is a great product with a great team behind it ...

This was a huge list so I won't cut and paste it. What looked very interesting was the first 4 lines: du: cannot access '/proc/914537/task/914537/fd/4': No such file or directory du: cannot access '/proc/914537/task/914537/fdinfo/4': No such file or directory du: cannot access '/proc/914537/fd/3 ...

It may be a bug in solusVM or something wrong with the host. If the disk were full it should be showing as full from the host node. However I cannot say with any certainty that this is an issue with keyhelp. I don't know what's happening. I'll contact support at my hosting provider and see if I can ...

I did a default install through solusVM. I assume that a default install would put everything in /, but maybe it has been customized on the host side. Here is the output of df -h Filesystem Size Used Avail Use% Mounted on udev 463M 0 463M 0% /dev tmpfs 99M 12M 87M 12% /run /dev/vda1 24G 23G 0 100 ...

I ran the "Calculate Disk Space" before I posted this thread. No errors. The disk calculator logs appear to be working properly. Here is copy and paste from the last run: [16-Feb-2023 20:46:01] INFO | Loading client accounts... [16-Feb-2023 20:46:01] INFO | Collecting data for client "lucky" [16-Feb ...

STOP - Please read the next lines carefully! 1) Please fill out the post template below completely! 2) The members of this forum provide their valuable time to help! In return, please provide as much information as possible and be specific in your error description. Posts that show little initiative ...