BOOT DISK ALMOST FULL

[10m]

Hello.

The boot disk on my 3CX server is 83% full. I do not have the recordings stored on the boot disk and few if any large directories. Here are the results of some of the commands I ran.


df -lh

Filesystem Size Used Avail Use% Mounted on
udev 3.8G 0 3.8G 0% /dev
tmpfs 779M 17M 763M 3% /run
/dev/sda1 79G 63G 13G 83% /
tmpfs 3.9G 24K 3.9G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sdb1 98G 11G 83G 11% /mnt/disk
tmpfs 779M 0 779M 0% /run/user/0

sudo du -Sh | sudo sort -rh | sudo head -5

du: cannot access './proc/15875/task/15875/fd/4': No such file or directory
du: cannot access './proc/15875/task/15875/fdinfo/4': No such file or directory
du: cannot access './proc/15875/fd/3': No such file or directory
du: cannot access './proc/15875/fdinfo/3': No such file or directory
6.5G ./mnt/NewRecordings/Recordings/517
5.4G ./var/lib/3cxpbx/Instance1/Data/Http/Reports
5.2G ./mnt/NewRecordings/Recordings/552
4.9G ./mnt/NewRecordings/Recordings/515
4.4G ./mnt/NewRecordings/Recordings/520

Your assistance is appreciated. I have more than 1 server with this hard disk approaching capacity issues.

 

[10m]

That is my confusion. I have another disk 100GB mounted to this Linux Server. But I'm realizing that the additional disk is somehow on the boot drive and the amount of free space available (from the dashboard) reduces with time as the recordings increase. Can someone please explain how the additional drive is still considered as part of the boot disk?

 

[10m]

I believe I have sorted out my confusion. The additional 100GB drive mount point is at /mnt/disk. ./mnt/NewRecordings is part of the boot drive (sda1). I deleted the files in ./mnt/NewRecordings, and the available space increased.