Storage space is getting critically high on the following drives of your system:

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

Update your sysadmin module should resolve this incorrect notice.

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

[root@freepbx-a ~]# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg_ha-slash
48380792 5518108 40405084 13% /
tmpfs 1962344 60488 1901856 4% /dev/shm
/dev/sda1 495844 34220 436024 8% /boot
/dev/drbd2 41621496 9524904 29982304 25% /drbd/mysql
/dev/drbd3 41621496 3983464 35523744 11% /drbd/httpd
/dev/drbd4 31216640 176064 29454860 1% /drbd/spare
/dev/drbd1 83243020 53367540 25646904 68% /drbd/asterisk
[root@freepbx-a ~]#

[root@localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
50G 37G 11G 79% /
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

Why /dev/mapper/VolGroup-lv_root 37Full

OK found the script that does this check and generates the alert but its encrypted so cant see what’s doing, but it does seem to be in error:-

[asterisk@freepbx-a asterisk]$ /var/lib/asterisk/bin/storage.php
email_sent

User-Agent: OSS FreePBXDistro;86258644;6.12.65-23
Date: Tue, 23 Dec 2014 14:40:13 +0000
From: “Schmoozecom Alerts” [email protected]
Return-Path: [email protected]
Bcc: [email protected]
Reply-To: "[email protected]" [email protected]
X-Sender: [email protected]
X-Mailer: OSS FreePBXDistro;86258644;6.12.65-23
X-Priority: 3 (Normal)
Message-ID: [email protected]
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
=?utf-8?Q?Critical_Storage_Alert_for_86258644.deployments.pbxact.com?=
Storage space is getting critically high on the following drives of your
system:
/dev/mapper/vg_ha-slash is 100% full

[asterisk@freepbx-a asterisk]$ df -k /dev/mapper/vg_ha-slash
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg_ha-slash
48380792 5518164 40405028 13% /
[asterisk@freepbx-a asterisk]$
[asterisk@freepbx-a asterisk]$
[asterisk@freepbx-a asterisk]$

For some reason the test is seeing /dev/mapper/vg_ha-slash as 100% full when in fact its 13% used.

[root@localhost ~]# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
51606140 38302936 10681764 79% /
tmpfs 1871232 0 1871232 0% /dev/shm
/dev/sda1 495844 34194 436050 8% /boot
/dev/mapper/VolGroup-lv_home
424786304 202992 403005380 1% /home

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.

I’ve been getting emails saying:

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
[root@pbx ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_backuppbx-lv_root
                       50G  8.4G   39G  18% /
tmpfs                 490M     0  490M   0% /dev/shm
/dev/sda1             485M   34M  426M   8% /boot
/dev/mapper/vg_backuppbx-lv_home
                       96G  188M   91G   1% /home

ok

when delete all backup and all calls why 46% full no recording calls and no backup

and i know why writing on /dev/mapper/VolGroup-lv_root and /dev/mapper/VolGroup-lv_home no writing any thing

[root@localhost ~]# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
51606140 22290536 26694164 46% /
tmpfs 1871232 0 1871232 0% /dev/shm
/dev/sda1 495844 34194 436050 8% /boot
/dev/mapper/VolGroup-lv_home
424786304 202992 403005380 1% /home

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

Thank you for any suggestions.

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.

2 Likes

Lorne,

Thank you. You’re exactly right. I disabled the backups and the problem stopped for several days. Re-enabled and the alert emails started back.

I’ll try to figure out other options (maybe exclude recordings and setup separate sync), or make a new post.