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

[apfan]

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

 

[apfan]

Mu host suggested that i used rm -rf file/
Nut i am sceptic about the whole thing

 

[Infopro]

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]

I have noticed those threads but i still can not solve the problem.

 

[apfan]

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

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

 

[apfan]

Bump

 

[Infopro]

It seems that i have a problem in / but how can i access it?

Thanks

You access your file system on the server via SSH. If you're unsure on how to do that you might want to look into this before attempting to delete any file via command line.

Or you might wish to hire someone.

You can find a list available at this link: Dev & Sys Admin Services - cPanels Application Catalog

 

[apfan]

I have contacted cpanel now!

 

[zestylemon]

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]

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

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.