disk warning

Lauren Raymond

• May 07, 2025 13:05

Hi

For the last 2 days I am receiving emails from the server saying
"The filesystem “/” mounted at “/” reached “warn” status because you currently use 82.93% of its available blocks."

/dev/sdb2        70G   59G   12G  84% /
has been at 63% for a long time In the last couple of days it is rising 83% yesterday and 84% today in df -h

I rebooted the server yesterday and it did not solve the problem.

[root@host2 ~]# df -h

Filesystem      Size  Used Avail Use% Mounted on

devtmpfs        4.0M     0  4.0M   0% /dev

tmpfs            16G     0   16G   0% /dev/shm

tmpfs           6.3G  178M  6.1G   3% /run

/dev/sdb2        70G   59G   12G  84% /

/dev/sdb1       1.7T  259G  1.5T  16% /home

/dev/sda1       2.7T  1.1T  1.6T  41% /backup

/dev/loop0      3.2G   91M  2.9G   3% /tmp

tmpfs           3.2G  4.0K  3.2G   1% /run/user/0

[root@host2 ~]#

 

[root@host2 ~]# df -i

Filesystem        Inodes   IUsed     IFree IUse% Mounted on

devtmpfs         4070307     622   4069685    1% /dev

tmpfs            4075291       1   4075290    1% /dev/shm

tmpfs             819200    1211    817989    1% /run

/dev/sdb2       25121384  274701  24846683    2% /

/dev/sdb1      178437312 3128542 175308770    2% /home

/dev/sda1      183140352   38392 183101960    1% /backup

/dev/loop0        214272     567    213705    1% /tmp

tmpfs             815058      25    815033    1% /run/user/0

[root@host2 ~]#

 

[root@host2 ~]# du -h --max-depth=1 / 2>/dev/null | sort -hr

1.4T    /

1.1T    /backup

246G    /home

49G     /var

8.7G    /usr

528M    /opt

389M    /boot

186M    /run

91M     /tmp

53M     /root

35M     /etc

4.0K    /home2

0       /sys

0       /srv

0       /proc

0       /mnt

0       /media

0       /dev

0       /afs

Any advice would be greatly appreciated

Thanks

Lauren

• 

  cPRex Jurassic Moderator

  • May 07, 2025 14:07

  Hey there!  I wouldn't expect a reboot to help with disk space issues.  Since you've already run the "du" command you can see where the space is being used - I would compare that to tomorrow's usage to see if you can find an area that is obviously increasing.  There really isn't another way around it or a fancier way to see the disk usage.  Using "du" and going down into each directory is the best way to find things you can remove from the system.

  0
• 

  Lauren Raymond

  • May 07, 2025 14:10

  Thanks for your help. 

  I see a lot of files in cd /tmp that look like these

  cloner-cert-0b0ad5801b41596c25457955f87092c4

  systemd-private-30eaa47a11894e54be69bb9f7efaf96f-kdump.service-nBIjN7

  Is it safe to delete these files?

   

   

  0
• 

  cPRex Jurassic Moderator

  • May 07, 2025 14:15

  I'm not familiar with the "cloner-cert" files so i can't say.

  The systemd directories you mention are likely in use by other things on the system so I would not remove those.  I doubt those are very large, though.

  0
• 

  Lauren Raymond

  • May 07, 2025 14:17

  Thanks again

  I see a lot of old logs - is it safe to delete these?

  [root@host2 ~]# cd /var

  [root@host2 var]# cd log

  [root@host2 log]# ls

  anaconda               dnf.rpm.log.1               maillog-20250427

  apache2                dnf.rpm.log.2               maillog-20250504

  audit                  dpkg.log                    messages

  boot.log               exim_mainlog                messages-20250413

  boot.log-20250330      exim_mainlog-20250413.gz    messages-20250420

  boot.log-20250405      exim_mainlog-20250420.gz    messages-20250427

  boot.log-20250409      exim_mainlog-20250427.gz    messages-20250504

  boot.log-20250415      exim_mainlog-20250504.gz    mysqld.log

  boot.log-20250423      exim_paniclog               named

  boot.log-20250430      exim_paniclog-20250413.gz   private

  boot.log-20250507      exim_paniclog-20250420.gz   quota_enable.log

  btmp                   exim_paniclog-20250427.gz   README

  btmp-20250501          exim_paniclog-20250504.gz   sa

  chkservd.log           exim_rejectlog              samba

  chrony                 exim_rejectlog-20250413.gz  secure

  cpanel-install.log     exim_rejectlog-20250420.gz  secure-20250413

  cpanel-server-traffic  exim_rejectlog-20250427.gz  secure-20250420

  cron                   exim_rejectlog-20250504.gz  secure-20250427

  cron-20250413          firewalld                   secure-20250504

  cron-20250420          hawkey.log                  spooler

  cron-20250427          hawkey.log-20250413         spooler-20250413

  cron-20250504          hawkey.log-20250420         spooler-20250420

  dcpumon                hawkey.log-20250427         spooler-20250427

  dnf.librepo.log        hawkey.log-20250504         spooler-20250504

  dnf.librepo.log.1      imav-deploy.log             sssd

  dnf.librepo.log.2      imunify360                  sw-cp-server

  dnf.librepo.log.3      imunify360_user_logs        tallylog

  dnf.librepo.log.4      kdump.log                   tuned

  dnf.log                lastlog                     wp-toolkit

  dnf.log.1              lfd.log                     wtmp

  dnf.log.2              lfd.log-20250504.gz         wtmp-20241014

  dnf.log.3              maillog                     xferlog.offsetftpsep

  dnf.log.4              maillog-20250413

  dnf.rpm.log            maillog-20250420

  [root@host2 log]#

  0
• 

  cPRex Jurassic Moderator

  • May 07, 2025 14:51

  Those are up to you - if you no longer need that log data then they would generally be safe to delete.  Don't delete any of the main logs, like dnf.rmp.log or maillog but things like exim_paniclog-20250504.gz  would be safe to remove.

  0
• 

  Lauren Raymond

  • May 07, 2025 14:54

  Excellent - thanks for your help and great advice. I changed the log rotation in the WHM tweak settings and if the old logs do not delete I will delete some of those logs that are not mail logs. Have a great day

  0
• 

  cPRex Jurassic Moderator

  • May 07, 2025 15:10

  Sounds good - you have a great day as well!

  0

Please sign in to leave a comment.