Well, doing a df I see that / is the 9.1G partition and the other one is /home.
Prior to cleaning, the partition was 9.05G full, after doing the cleanup it is now down to 8.7G. so I have got to see what all is in it. Or I will have to make it bigger. I have a boat load of empty space on the HD so I can shrink home a bit and give it some more space, but if it is just going to eat that up with some blackhole files I need to find out what they are and see what can be trimmed. / is /dev/sda1 /home is /dev/sda5 Here is what df returns kp4djt@kp4djt64:~$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 10193624 0 10193624 0% /dev tmpfs 2044984 1468 2043516 1% /run /dev/sda1 9649432 8647828 491716 95% / tmpfs 10224912 41984 10182928 1% /dev/shm tmpfs 5120 8 5112 1% /run/lock tmpfs 10224912 0 10224912 0% /sys/fs/cgroup /dev/loop0 89472 89472 0 100% /snap/ubuntu-mate-welcome/217 /dev/loop1 89984 89984 0 100% /snap/core/5742 /dev/loop2 89216 89216 0 100% /snap/ubuntu-mate-welcome/199 /dev/loop3 7808 7808 0 100% /snap/pulsemixer/8 /dev/loop5 73472 73472 0 100% /snap/software-boutique/31 /dev/loop4 8192 8192 0 100% /snap/pulsemixer/23 /dev/loop6 89984 89984 0 100% /snap/core/5662 /dev/loop7 89984 89984 0 100% /snap/core/5548 /dev/loop8 89472 89472 0 100% /snap/ubuntu-mate-welcome/208 /dev/sda5 462268272 231803916 206912664 53% /home tmpfs 2044980 44 2044936 1% /run/user/1000 /dev/sdb2 483946 245149 213812 54% /media/kp4djt/172b795b-0a64-4265-a747-c5d65c6f606d /dev/mapper/ubuntu--mate--vg-root 952137676 255183348 648565416 29% /media/kp4djt/9b4c4135-80c2-42c3-a2ac-8376e6964e7a On Sun, Nov 4, 2018 at 10:17 PM Larry Brigman <larry.brig...@gmail.com> wrote: > Use 'df' to see what partitions are in use and percentage. > > On Sun, Nov 4, 2018, 8:14 PM Bill Barry <b...@billbarry.org wrote: > > > On Mon, Nov 5, 2018 at 3:40 AM Chuck Hast <wch...@gmail.com> wrote: > > > > > I went in and was able to boot to the previous image. The recovery > > offered > > > to remove all > > > unneeded files, then did the update. I was able to restart it. For > > > some reason it reported > > > that root was full, but (I double checked this) it was saying "root". > > There > > > is a "root " directory > > > in the boot directory, it is normally only accessed by root I do a > chmod > > to > > > it to get into it, then > > > I change it back once done. There is not much in there. So seems the > real > > > issue is boot. > > > > > > I have purged out all old images, but seems that boot should not come > > near > > > filling up a > > > 9.1G directory, at least to me. I see a lot of stuff but not sure > what. I > > > think I am going to > > > increase the size of boot so that this doesn't happen again again. I > > > generally try to keep no > > > more than 2 older kernels. > > > > > > Only partitions get full, not directories. Is /boot in a separate > > partition than / ? If not then check your partition structure and see > which > > partition is full and clean it out or make it bigger. > > > > Bill > > _______________________________________________ > > PLUG mailing list > > PLUG@pdxlinux.org > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > -- Chuck Hast -- KP4DJT -- I can do all things through Christ which strengtheneth me. Ph 4:13 KJV Todo lo puedo en Cristo que me fortalece. Fil 4:13 RVR1960 _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
