Running low on space HA yellow

Installation Home Assistant OS
1

Hello all,
i noticed i am running low on space (Settings → System → Storage). I asked this on discord but i though maybe also here will be bigger reach.
I followed Check Space · GitHub
But i’m definitely not getting the right answers there. It seems all space is referred from inside of the container. I did install advanced SSH and i’m using web UI.

➜  ~ du -shc /* | sort -h
0       /config
0       /dev
0       /proc
0       /sys
4.0K    /addons
4.0K    /init
4.0K    /lib64
4.0K    /media
4.0K    /mnt
4.0K    /opt
4.0K    /srv
12.0K   /home
12.0K   /ssl
16.0K   /share
28.0K   /addon_configs
40.0K   /data
52.0K   /command
80.0K   /tmp
632.0K  /run
756.0K  /sbin
1.6M    /lib
1.7M    /etc
3.2M    /bin
10.1M   /package
14.7M   /root
316.6M  /usr
432.1M  /homeassistant
502.8M  /var
708.8M  /backup
1.9G    total

➜  ~ df -h               
Filesystem                Size      Used Available Use% Mounted on
overlay                 220.0G    209.2G      1.8G  99% /
devtmpfs                  3.8G         0      3.8G   0% /dev
tmpfs                     3.8G         0      3.8G   0% /dev/shm
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /backup
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /data
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /homeassistant
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /share
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /addons
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /media
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /ssl
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /addon_configs
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /run/audio
tmpfs                     3.8G         0      3.8G   0% /dev/shm
tmpfs                     1.5G      1.7M      1.5G   0% /run/docker.sock
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /etc/asound.conf
tmpfs                     1.5G      1.7M      1.5G   0% /run/dbus
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /etc/resolv.conf
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /etc/hostname
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /etc/hosts
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /etc/pulse/client.conf
tmpfs                     1.5G      1.7M      1.5G   0% /run/log/journal
/dev/nvme0n1p1          220.0G    209.2G      1.8G  99% /var/log/journal
tmpfs                     3.8G         0      3.8G   0% /proc/asound
devtmpfs                  3.8G         0      3.8G   0% /proc/keys
devtmpfs                  3.8G         0      3.8G   0% /proc/latency_stats
devtmpfs                  3.8G         0      3.8G   0% /proc/timer_list
tmpfs                     3.8G         0      3.8G   0% /sys/firmware

Please any hints on how to proceed?

2

Mistake i made was the docker commands on the github link above.

After querying space on OS, my suspicion of influxdb causing this was confirmed so i dropped many things there were collected for no reason and DB is about 30GB now with plenty of space to spare.

3

I only record the sensors I want in influxdb.
I probably only record 20 sensors max in my database now.
Previous everything was recorded, creating huge back-ups.

In configuration.yaml

influxdb:
  include:
    entities:
      - sensor.sensor_i_want_long_term_stats_on
    ...