Recursive config folder?

I don’t know if it’s just me or not, can’t find any info on this…
When using “core_configurator” file editor or when browsing config files using samba share, I see a config folder inside the config folder that leads to… the same files, only a level lower. And they work.
I can go config/config/config/… as long as I want ^^

This is not a big deal at first sight, but my config folder is huge, like 7 Go and I control the size of the history database by putting only things I need in it, so the problem is not the db file.
As a matter of fact all the config files make up to a measly 180 Mo… It’s only the config folder inside the config folder that takes 7Go, that’s what worries me.

Anyone has the same problem ? Any idea what could be the cause ?
Using HA dockerised in a debian virtual machine on synology NAS.
Thx

You should run fsck. Your file-system is probably corrupt.

Thanks for the suggestion, tried fsck -R -A on the VM, gave nothing. Tried touch /forcefsck nothing either.
No change after reboot.

Happend here on a RPI4, Debian 11, HA Supervised too. Nothing wrong with the file system as you have found that out already but the culprit seems to be a bad (infinite) symlink:

/usr/share/hassio/homeassistant/config -> /config -> /config -> /config —> and so on wihout end.

I solved it by using the CLI (SSH) cd-ing into the root of the config directory:
cd /usr/share/hassio/homeassistant

and simply ran:
unlink config

After the unlinking those infinite config directories were gone.

2 Likes

Works like a charm, thanks !