2

I tried unzipping a 37MB RAR file, but system says root is full. I used sudo baobab / to check, and it shows that / takes up 14.1GB. It acknowledges the fact that the free space exists, but it still shows root as full. I ran sudo du -h in root and it shows 19GB. I ran sudo df -i and it shows:

Filesystem      Inodes  IUsed   IFree IUse% Mounted on
/dev/sda5      3244032 321772 2922260   10% /

I ran sudo df -h --total and it shows:

Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           394M  1.5M  393M   1% /run
/dev/sda5        49G   14G   33G  29% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/loop0      221M  221M     0 100% /snap/code/63
/dev/loop1      208M  208M     0 100% /snap/code/65
/dev/loop3       99M   99M     0 100% /snap/core/11081
/dev/loop2      100M  100M     0 100% /snap/core/10958
/dev/loop5       56M   56M     0 100% /snap/core18/2066
/dev/loop4       56M   56M     0 100% /snap/core18/1997
/dev/loop6      218M  218M     0 100% /snap/gnome-3-34-1804/60
/dev/loop7      219M  219M     0 100% /snap/gnome-3-34-1804/66
/dev/loop8       65M   65M     0 100% /snap/gtk-common-themes/1514
/dev/loop9       66M   66M     0 100% /snap/gtk-common-themes/1515
/dev/loop11      52M   52M     0 100% /snap/snap-store/518
/dev/loop10      52M   52M     0 100% /snap/snap-store/498
/dev/loop12      33M   33M     0 100% /snap/snapd/11588
/dev/loop13      33M   33M     0 100% /snap/snapd/11841
/dev/sda1       511M  4.0K  511M   1% /boot/efi
tmpfs           394M   60K  394M   1% /run/user/1000
total            58G   15G   40G  27% -

I used xdiskusage in two different ways: sudo xdiskusage / , which showed 13.11GB, and sudo xdiskusage and then chose from the graphical interface the disk / is mounted on, which showed 48.6GB, from which 32.94 is (free), 2.49 is (inodes) and the rest is the actual root.

sudo fdisk -l

Disk /dev/sda: 50 GiB, 53687091200 bytes, 104857600 sectors Disk model: VBOX HARDDISK
Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xee2b9e47

Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1050623 1048576 512M b W95 FAT32 /dev/sda2 1052670 104857599 103804930 49.5G 5 Extended /dev/sda5 1052672 104855551 103802880 49.5G 83 Linux

The system is running on VMBox. It was initially allocated at 25GB but I expanded the partition into 50 using GParted. The problem started before I messed with the partitioning. I have rebooted the system, in case open but not deleted files are there. No large log files are present (only 349MB).

1 Answers1

-1

I had a root partition report full on Mom's computer (Kubuntu 16.04). The solution was to run: sudo apt autoremove
In that case the update program never cleaned out the old files. Now running 20.04, it runs fine.