Wondering how to resolve cPanel partition disk space is full error? We can help you.

As part of our Server Management Services, we assist our customers with similar cPanel queries.

Today, let us see how our Support techs resolve this.

How to resolve cPanel partition disk space is full error?

Today, let us see the steps followed by our Support Techs to address and find out what is consuming most of the disk space.

Firstly, you would need to confirm if the disk space is indeed nearly full.

You can check this by the df command.

df -hCopy Code

You should see an output similar to below:

df -hCopy Code

Filesystem Size Used Avail Use% Mounted on

devtmpfs 7.7G 0 7.7G 0% /dev

tmpfs 7.7G 7.6M 7.7G 1% /dev/shm

tmpfs 7.7G 59M 7.7G 1% /run

tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup

/dev/mapper/centos-root 50G 37G 14G 73% /

/dev/sda1 1014M 351M 664M 35% /boot

/dev/mapper/centos-home 1.8T 2.6G 1.8T 1% /home

/dev/loop0 2.2G 195M 1.9G 10% /tmp

tmpfs 1.6G 4.0K 1.6G 1% /run/user/42

tmpfs 1.6G 40K 1.6G 1% /run/user/0Copy Code

According to the output above, you can see

/dev/mapper/centos-rootCopy Code

is at 73% full.

Therefore, we should be investigating that partition alone.

Since

/dev/mapper/centos-rootCopy Code

is the root partition, it includes all the other partitions.

It is important to ensure we are excluding other partitions when checking the disk space.

Else, the disk space is going to take a very long while to calculate.

Once you have determined the directory that is consuming the most disk space, you can use the command below to get a more detailed read-out.

du -h --max-depth=1 -x /$partition | sort -hrCopy Code

We are using -x, because we are reading for –one-file-system. This skips directories on different file systems

Replace $partition with the complete file path.

For example:

# du -h --max-depth=1 -x /usr | sort -hrCopy Code

21G /usr

14G /usr/share

2.9G /usr/local

2.1G /usr/lib64

1.2G /usr/lib

413M /usr/bin

272M /usr/src

181M /usr/sbin

152M /usr/libexec

40M /usr/include

0 /usr/selector.etc

0 /usr/selector

0 /usr/games

0 /usr/etcCopy Code

From the output above you could see within /usr directory, /usr/share/ is the directory that is using a lot of disk space.

You could run the same command once more on /usr/share/ to calculate the details.

# du -h --max-depth=1 -x /usr/share | sort -hrCopy Code

Once you have determined which directory consumed a lot of the disk space, then you can review individual files and sections of that directory to see if anything is using more space than it should.

Often at time, this maybe a log file that has never been cleared, or backups that were forgotten about.

You can then perform any necessary actions to have the cause of the increased disk space addressed properly.