Ubuntu: low disk space (but not)

Software & Operating Systems Linux
#1

I’m running out of ideas here and hope someone will have some good input.

I’m running Ubuntu Gnome 17.04. my boot drive is 250GB. 500MB each for /boot and /boot/efi, and the rest is formatted as crypt-luks. 32GB of that is swap, then 15GB each for /var and /tmp, and the rest is /.

My /home directory is a second 250GB drive.

A few days ago, ubuntu started showing me notices about running out of disk space. I get a warning about “only {small number like 500MB} remaining on filesystem root.” I’m even starting to get errors from some commands that write to /tmp about having no space left to write. However, disk usage analyzer shows i’m only using ~ 8GB.

I opened up gparted and it tells me that the crypt-luks partition isn’t mounted. This doesn’t make sense — I can access files, run programs, and so forth. There’s a message,

Warning: Linux Unified Key Setup encryption is not yet supported.

…which I don’t remember seeing before, but encryption is set up successfully on boot (and, as noted above, reading/writing files works just fine).

Any suggestions? Appreciate it!

edit

ok, a discovery:

~$ df -h
Filesystem                          Size  Used Avail Use% Mounted on
udev                                 16G     0   16G   0% /dev
tmpfs                               3.2G   11M  3.2G   1% /run
/dev/mapper/ubuntu--gnome--vg-root  196G  185G  1.1G 100% /
tmpfs                                16G   82M   16G   1% /dev/shm
tmpfs                               5.0M  4.0K  5.0M   1% /run/lock
tmpfs                                16G     0   16G   0% /sys/fs/cgroup
/dev/sdb1                           234G  150G   73G  68% /home
/dev/sda1                           235G   85G  139G  38% /mnt/phison-white
/dev/nvme0n1p2                      465M  151M  286M  35% /boot
/dev/nvme0n1p1                      511M  3.4M  508M   1% /boot/efi
tmpfs                               3.2G   16K  3.2G   1% /run/user/120
tmpfs                               3.2G   44K  3.2G   1% /run/user/1000

what’s up with /dev/mapper ? is it reporting corrcet usage? how do i find what’s taking up all this space, if so?

1 Like
#2

Can you run apt autoremove
if you have a bunch of kernals that can sometimes cause a weird space issue

1 Like
#3

ran about two weeks ago, but running again:

~$ sudo apt autoremove
[sudo] password for adrian: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
#4

ugh… i think i’ve found it

i run VMs, and also a bunch of docker containers, for work. i have vagrant set up to store images on a separate disk, but apparently docker keeps overlay images in /var/lib/docker.

prevailing advice seems to be to rsync the directory somewhere else, and then mount that new directory as /usr/lib/docker. this seems… odd to me. has anyone dealt with this issue before?