Getting an insufficient space message. I’ve deleted a few things, but it keeps happening. All I have on this Vero is kodi and PlexKodiConnect. Looking at a post from a few years ago, I saw to run df -h, what ever that is. Here’s what that says:
This thread should give you a good place to start…
Most users that just have a fairly basic setup will only find issues with the thumbnails folder which can be safely deleted if that is where your space is being taken up. Kodi will recache artwork from the original source automatically and repopulate that folder.
I have no idea what I’m doing–barely able to ssh into this thing. Here’s what I get:
osmc@osmc:~$ sudo du -hs /*
7.2M /bin
19M /boot
0 /dev
14M /etc
12G /home
268M /lib
4.0K /lib64
16K /lost+found
8.0K /media
4.0K /mnt
3.5M /opt
du: cannot access ‘/proc/577/task/839/fd/69’: No such file or directory
du: cannot access ‘/proc/577/task/841/fdinfo/69’: No such file or directory
du: cannot access ‘/proc/577/task/842/fd/69’: No such file or directory
du: cannot access ‘/proc/577/task/843/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/845/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/846/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/847/fd/69’: No such file or directory
du: cannot access ‘/proc/577/task/849/fdinfo/69’: No such file or directory
du: cannot access ‘/proc/577/task/850/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/854/fdinfo/69’: No such file or directory
du: cannot access ‘/proc/577/task/855/fdinfo/67’: No such file or directory
du: cannot access ‘/proc/577/task/856/fdinfo/69’: No such file or directory
du: cannot access ‘/proc/577/task/886/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/886/fd/69’: No such file or directory
du: cannot access ‘/proc/577/task/887/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/894/fdinfo/67’: No such file or directory
du: cannot access ‘/proc/577/task/895/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/897/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/899/fdinfo/67’: No such file or directory
du: cannot access ‘/proc/577/task/900/fd/67’: No such file or directory
du: cannot access ‘/proc/577/task/902/fdinfo/69’: No such file or directory
du: cannot access ‘/proc/577/task/1038/fd/69’: No such file or directory
du: cannot access ‘/proc/577/task/1040/fdinfo/67’: No such file or directory
du: cannot read directory ‘/proc/2489/net’: Invalid argument
du: cannot access ‘/proc/20642/task/20642/fd/4’: No such file or directory
du: cannot access ‘/proc/20642/task/20642/fdinfo/4’: No such file or directory
du: cannot access ‘/proc/20642/fd/4’: No such file or directory
du: cannot access ‘/proc/20642/fdinfo/4’: No such file or directory
0 /proc
12K /root
17M /run
6.6M /sbin
4.0K /selinux
4.0K /srv
0 /sys
24K /tmp
700M /usr
227M /var
0 /walkthrough_completed
You may notice a little bit of slowdown in the UI as the thumbnails are initially regenerated. This is done on demand so it will be more of a little at a time as you scroll through your library and not a machine hanging for period of time as it deals with all of them at the same time. Also if you have any library items that are set with artwork that is no longer at the same location you will get empty art until you bring up the information window for that item and either refresh or manually select new art.
Basically the deal is that Kodi isn’t great about cleaning up dead artwork so under various situations there can be a large number of worthless files taking up space. There are various ways of dealing with this. The easiest and quickest is usually just dumping them and their database and let Kodi start over. Alternatives are using the Texture Cache Maintenance utility (which is more complicated to use) to selectively remove dead artwork or moving the thumbnail folder to a location with more space and doing a path substitution to redirect to that new location.
What you posted only adds up to around 3GB so whatever your issue I’m guessing it may not be space related. I would suggest to start a new thread with logs.