Harddisk is at or near capacity!

Status
Not open for further replies.

netventure

Forum User
Joined
Aug 9, 2019
Messages
4
Reaction score
0
After upgrading from V15 to V16 we now get emails telling us that disk space is running low (Same info in the Dashboard). As a result of this recordings are disabled until this problem is resolved.

In fact there should be enough disk space (as the drive was partitioned during the initial install) but 3CX seens not to see this space.

Is there any other solution than reinstalling the complete server?
 
What OS?
Was the drive set with one partition?
What size is the harddrive?
Does a file manager show you how much free space there is?
 
Are you saying that your OS and 3CX are seeing different drive sizes? So in the 3CX dashboard it says there is less than xxx space but when you look at the OS level you see more?
 
OS Debian 9.9
3CX 16.0.2.910
As there are different paritions, 3CX sees only the size of the root partition. Recordings and Backups have been moved to different partitions (due to the reason that the original drive was to small)
 
but when we talk that the root partition is small, how small are we talking?
 
/ = 1G, 469 MB used, 390 MB free
 
okey, your PBX is at risk! I must recommend reinstalling asap the PBX.
Even with logging off your rood device will eat for swap and co disc space and you wish not to be at 0 and find out you cannot boot into Linux anymore!
 
  • Like
Reactions: Evolute IT
OK. I already though that reinstalling would be the only 3CX compatible solution. It seems to me that the concept of putting different folder to different partitions is not in the linux installation concept of 3CX. For example if you do extra partitions for logging, swap and so on a full log partition will never cause the whole system to become unbootable.
 
OK. I already though that reinstalling would be the only 3CX compatible solution. It seems to me that the concept of putting different folder to different partitions is not in the linux installation concept of 3CX. For example if you do extra partitions for logging, swap and so on a full log partition will never cause the whole system to become unbootable.
I had done this once. Installed Debian and create a partition for /var. It was a bad idea since backups and recordings are in /var/lib/3cxpbx. The server would fill up and stop working since you can't run processes if /var is full.

I had to reinstall the system and now I always use the "1 partition for everything" and just do backups on Google Drive or SFTP.
 
Even if you want to put things in seperate partitions, i am constantly beating up other IT Guys with the simple fact of, You do not create a root or c: drive with a tiny amount of space for the base OS with the assumption everything else will go to a different drive/partition, Always overspec the root/C: drive beyond what you expect for updates/patches/future. I see too many servers with root/c: drives totally full because some bonehead set them up with 5 GB, 10 GB and assigned all the rest of the space to a second map/drive letter without taking into any account, the growth from updates, swap usage, future changes, etc.

We thin provision all of our virtual linux 3CX servers with no less than 50 GB such that there is also a decent space for recordings and backups, and if we start to run that limit, we add space, or add a new virtual disk with say 100-200gb and set backups and recordings to there, and flush them out of the main partition.

Wasteful as it may seem, we set the windows boxes to thin provision of 100-200 GB as the newer versions of windows server love to pile on windows updates like a trash pile into the winsxs folder and fill up disks needlessly, and even the dism tool will not clean it out to any respectable level, windows update is a wasteful dumpster fire.
 
  • Like
Reactions: technigogo
Status
Not open for further replies.

Forum statistics

Threads
111,933
Messages
589,809
Members
164,808
Latest member
jsbjsb