Panic Drive Critical: /dev/xvda3 (/) is 95% full

apfan

Member
Jun 6, 2005
23
0
151
Iceland
I have panic here what should i do to resolve this?
O have putty installed and i know some basic comands trought ssh.
I also on vps linux witc centos :confused:
 

Infopro

Well-Known Member
May 20, 2003
17,090
516
613
Pennsylvania
cPanel Access Level
Root Administrator
Twitter
If you scroll to the bottom of this thread you'll see some links to similar threads to this one. If you visit those links, do the same thing there. Scroll down to see links to similar threads.

There are many many threads on this topic of "Drive Critical" that you may find useful.
 

apfan

Member
Jun 6, 2005
23
0
151
Iceland
Code:
My SSH df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/xvda3            7.2G  6.5G  407M  95% /
/dev/xvda1             99M   23M   71M  25% /boot
tmpfs                 128M     0  128M   0% /dev/shm
/usr/tmpDSK           485M   11M  449M   3% /tmp

Code:
du -sh /*
24K     /aquota.user
7.8M    /bin
22M     /boot
44K     /dev
89M     /etc
1.3G    /home
332M    /lib
22M     /lib64
16K     /lost+found
8.0K    /media
0       /misc
8.0K    /mnt
0       /net
28M     /opt
0       /proc
60K     /quota.user
5.9M    /root
33M     /sbin
5.1M    /scripts
8.0K    /selinux
8.0K    /srv
0       /sys
395K    /tmp
4.1G    /usr
574M    /var
It seems that i have a problem in / but how can i access it?

Thanks
 

Infopro

Well-Known Member
May 20, 2003
17,090
516
613
Pennsylvania
cPanel Access Level
Root Administrator
Twitter

zestylemon

Member
Jul 19, 2010
10
0
51
cPanel, by default, creates a loopback device that mounts to /tmp. The default size is only 512MB. This is quite small and quite common for a cPanel server to need a larger /tmp partition. Follow these instructions on /http://adamstechblog.com/2009/11/03/resize-tmp-partition-on-cpanel/.
 

cPanelDon

cPanel Quality Assurance Analyst
Staff member
Nov 5, 2008
2,545
12
268
Houston, Texas, U.S.A.
cPanel Access Level
DataCenter Provider
Twitter
Code:
My SSH df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/xvda3            7.2G  6.5G  407M  95% /
/dev/xvda1             99M   23M   71M  25% /boot
tmpfs                 128M     0  128M   0% /dev/shm
/usr/tmpDSK           485M   11M  449M   3% /tmp

Code:
du -sh /*
24K     /aquota.user
7.8M    /bin
22M     /boot
44K     /dev
89M     /etc
1.3G    /home
332M    /lib
22M     /lib64
16K     /lost+found
8.0K    /media
0       /misc
8.0K    /mnt
0       /net
28M     /opt
0       /proc
60K     /quota.user
5.9M    /root
33M     /sbin
5.1M    /scripts
8.0K    /selinux
8.0K    /srv
0       /sys
395K    /tmp
4.1G    /usr
574M    /var
It seems that i have a problem in / but how can i access it?

Thanks
The root "/" partition size appears to be too small in comparison to the needs of how much data is being stored there. Based on the output provided, it would appear to me that your "/home" directory path, that usually contains the majority of account data from hosted sites and users, as well other sizable areas, like "/usr", are all being stored within the root "/" partition on your server.

I recommend adding another disk drive to relocate some of the data, such as relocating the "/home" directory to its own partition on a new hard drive so that space is freed and made available on the existing root "/" partition. Your upstream server or hosting provider can assist with installing and provisioning more hard drives for expanded storage capacity.

If adding hard drives is not an option, in my professional opinion, I would consider migrating to a new server that uses a significantly larger root "/" partition in addition to using a separate hard drive or larger partition to store the "/home" directory.

cPanel, by default, creates a loopback device that mounts to /tmp. The default size is only 512MB. This is quite small and quite common for a cPanel server to need a larger /tmp partition.
I see no information that would indicate an issue with the "/tmp" partition; the detail provided leads me to believe the reported problem stems from the small size of the root "/" partition and the increasing disk usage requirements of the affected system.