I have two disks in my system. The original disk I started with and now a new SSD which I recently added.
I then moved “data” to a new Data Drive using the move data disk option. Went without a hitch and then migrated my DB into mariaDB and configured influxDB. Sort of normal two months in activity I suspect.
Here is the thing.
HA-OS basically copies the docker instances to the new disk and reboots itself. I know this because I use a dev HA instance on a VM where I can use checkpoints, mount disks elsewhere, boot from other Linux disks and generally get under the covers to do what I want without fear of wrecking anything.
I am not finding any documentation on how to reclaim the space used by the “original” data files in the original docker instances before they were “moved”.
I now see two volumes one called “hassos-data” on the new data disk and one called “hassos-data-old” on the original disk. However, I do not see any docs which say, sure, go ahead and delete data-old which I would expect.
Does anyone know how to do about this?
Docker shows that the current containers are all pointing to mnt/
docker ps -q | xargs -I {} docker inspect --format='{{.Name}}: {{.GraphDriver.Data.MergedDir}}' {}
/homeassistant: /mnt/data/docker/overlay2/1a28d22acd8b043578d158695e7b385a41167e1b88e5b1c066c9c3381829760c/merged
/addon_a0d7b954_phpmyadmin: /mnt/data/docker/overlay2/fbadef6c322a4f569b88e7477fa5d48e8cb7873c44abd073dbf39af37890b34a/merged
/addon_77c0fc0d_mqtt-explorer: /mnt/data/docker/overlay2/787dd7ee5f4f5ee478309dbb46817101740e14a36305693277c3179f07953a91/merged
/addon_9074a9fa_cloudflared: /mnt/data/docker/overlay2/d834a23b1475bbcb2dc2a115626b68c1cc754921d2d3bd11d993e7dd8e1b2fe9/merged
/addon_core_configurator: /mnt/data/docker/overlay2/854e7d897281a6a8f379dfecd24bfbf677c0f7e385c02c47f0f69e1255ac8071/merged
/addon_a0d7b954_grafana: /mnt/data/docker/overlay2/dc0b563ce08e02e87da712173ba55c1b9b55db09c56c1db4c113d7a487b21b4e/merged
/addon_a0d7b954_ssh: /mnt/data/docker/overlay2/c1893ff59061cb9288aa5b96bb95b5723d11f1aa0a0a00b62116ac2fec59755c/merged
/addon_a0d7b954_influxdb: /mnt/data/docker/overlay2/ba4e168f2f491e8760da64742aa83b5524d6162b82db03cc24c9530599278731/merged
/addon_5c53de3b_esphome: /mnt/data/docker/overlay2/9ff159d2cf30bcbb31057d2335fe3cced04aded10bfe70a4fc35c4e215f108f0/merged
/addon_core_ssh: /mnt/data/docker/overlay2/481b6afbb2e5b5010ff349e83f7c1c8e01634c43f778213b0f1e4002e82edfa6/merged
/addon_core_samba: /mnt/data/docker/overlay2/fc5e6692774c764b7c3fec6128c1c11a27b07fc497c4a105325c3ffbf4c8f7f5/merged
/addon_core_mariadb: /mnt/data/docker/overlay2/54c55e681e5b0c4d3222ed504aa56bc7d30c4fa476b6f6d9e2129873a90ae5e4/merged
/addon_core_mosquitto: /mnt/data/docker/overlay2/d60c7d8f9e53c994573640651483ecd2156ca95fca50e832ac378a80d4188896/merged
/hassio_multicast: /mnt/data/docker/overlay2/38b9c7baa860dc79684390541b06bed0ea73cd8d4d956c1efbb46578a5f02cf5/merged
/hassio_audio: /mnt/data/docker/overlay2/8efc85a446207e97b4b50c138ce45d5b9fc647d985190c6c6607abba4fcccf38/merged
/hassio_dns: /mnt/data/docker/overlay2/31484bcc53bfb9304f4830a5614215af7e0c0462b371384b7677fd6d8a6d973b/merged
/hassio_cli: /mnt/data/docker/overlay2/a7b880fbf17a69dc6246f44f79edc8cedd6be6e704745d462a7b66dc16d468e8/merged
/hassio_supervisor: /mnt/data/docker/overlay2/7bbaa6a7a3a77d86cb4bb689fd4d65e437bd06c2532bca3d33bb9abf593f9186/merged
/hassio_observer: /mnt/data/docker/overlay2/987377773f791d7da97448b5b74ddf03cdfa342b3a9a5f9595977da3fca33846/merged
and
df -h
Filesystem Size Used Available Use% Mounted on
overlay 117.3G 14.3G 98.2G 13% /
/dev/sda1 117.3G 14.3G 98.2G 13% /media
/dev/sda1 117.3G 14.3G 98.2G 13% /addon_configs
devtmpfs 1.8G 0 1.8G 0% /dev
tmpfs 1.8G 0 1.8G 0% /dev/shm
/dev/sda1 117.3G 14.3G 98.2G 13% /ssl
/dev/sda1 117.3G 14.3G 98.2G 13% /addons
/dev/sda1 117.3G 14.3G 98.2G 13% /share
/dev/sda1 117.3G 14.3G 98.2G 13% /homeassistant
/dev/sda1 117.3G 14.3G 98.2G 13% /data
/dev/sda1 117.3G 14.3G 98.2G 13% /backup
tmpfs 749.1M 1.7M 747.5M 0% /run/dbus
tmpfs 1.8G 0 1.8G 0% /dev/shm
/dev/sda1 117.3G 14.3G 98.2G 13% /run/audio
tmpfs 749.1M 1.7M 747.5M 0% /run/docker.sock
/dev/sda1 117.3G 14.3G 98.2G 13% /etc/asound.conf
/dev/sda1 117.3G 14.3G 98.2G 13% /etc/resolv.conf
/dev/sda1 117.3G 14.3G 98.2G 13% /etc/hostname
/dev/sda1 117.3G 14.3G 98.2G 13% /etc/hosts
/dev/sda1 117.3G 14.3G 98.2G 13% /etc/pulse/client.conf
tmpfs 749.1M 1.7M 747.5M 0% /run/log/journal
/dev/sda1 117.3G 14.3G 98.2G 13% /var/log/journal
tmpfs 1.8G 0 1.8G 0% /proc/asound
tmpfs 1.8G 0 1.8G 0% /proc/acpi
devtmpfs 1.8G 0 1.8G 0% /proc/interrupts
devtmpfs 1.8G 0 1.8G 0% /proc/kcore
devtmpfs 1.8G 0 1.8G 0% /proc/keys
devtmpfs 1.8G 0 1.8G 0% /proc/timer_list
tmpfs 1.8G 0 1.8G 0% /proc/scsi
tmpfs 1.8G 0 1.8G 0% /sys/firmware
tmpfs 1.8G 0 1.8G 0% /sys/devices/system/cpu/cpu0/thermal_throttle
tmpfs 1.8G 0 1.8G 0% /sys/devices/system/cpu/cpu1/thermal_throttle
tmpfs 1.8G 0 1.8G 0% /sys/devices/system/cpu/cpu2/thermal_throttle
tmpfs 1.8G 0 1.8G 0% /sys/devices/system/cpu/cpu3/thermal_throttle
So it does look like sda1, the new disk is mounted at mnt/data and this is where all the containers are hanging from as it stands.
So, can I whack the hassos-data-old volume ? Or is there a way to have docker clean itself up? (I don’t think Docker has any reference to the containers in the old volume though).