Storage space is getting critically high on the following drives of your
system:
/dev/mapper/VolGroup-lv_root is 100% full /dev/mapper/VolGroup-lv_home is 100% full
nand there’s space full
[root@localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
50G 36G 12G 77% /
tmpfs 1.8G 0 1.8G 0% /dev/shm
/dev/sda1 485M 34M 426M 8% /boot
/dev/mapper/VolGroup-lv_home
406G 199M 385G 1% /home
Oddly today I have also started getting hourly emails saying a device is full but looking I think the error message is incorrect.
Which script is doing this check and generating the email?
Storage space is getting critically high on the following drives of your
system:
/dev/mapper/vg_ha-slash is 100% full
For anyone still having this issue (of receiving emails saying that your disk is full when it’s not), as @tonyclewis stated above, update your Sysadmin module, as we pushed a fix for this issue.
Subject: Critical Storage Alert for 34140593.deployments.pbxact.com
Storage space is getting critically high on the following
drives of your
system:
/dev/mapper/vg_backuppbx-lv_root is 100% full
/dev/mapper/vg_backuppbx-lv_home is 100% full
I’m not sure what that location is or how it got full. Here is the output of fdisk -l:
[root@pbx ~]#
Disk /dev/sda: 160.0 GB, 160000000000 bytes
255 heads, 63 sectors/track, 19452 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd0f4738c
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 19453 155736064 8e Linux LVM
Disk /dev/mapper/vg_backuppbx-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_backuppbx-lv_swap: 2080 MB, 2080374784 bytes
255 heads, 63 sectors/track, 252 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_backuppbx-lv_home: 103.7 GB, 103704166400 bytes
255 heads, 63 sectors/track, 12607 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
I am having this same issue now on FreePBX 14.0.11, with all 14.x system and module updates. I am getting daily emails saying /dev/mapper/SangomaVG-root is nearly full, but it isn’t:
[root@freepbx ~]# df -hl
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/SangomaVG-root 101G 66G 36G 65% /
devtmpfs 853M 0 853M 0% /dev
tmpfs 866M 460K 865M 1% /dev/shm
tmpfs 866M 92M 774M 11% /run
tmpfs 866M 0 866M 0% /sys/fs/cgroup
/dev/sda1 1.9G 117M 1.7G 7% /boot
tmpfs 174M 0 174M 0% /run/user/0
tmpfs 174M 0 174M 0% /run/user/995
Does the notice correspond to when a backup is running? Depending on how much there is to backup, there can be a considerable amount of dive space used for temp files which then get removed when the tarball is done.