Ok, this not exactly a complaint as much as it is an attempt to verify an observation. It seems that Logo’s file structure is very inefficient or at the very least very messy as it manages its files. I generally have between 11GB – 12GB of free disk space on my computer. But on occasion I’ll get a notice that the reindexing function has terminated because I don’t have enough free disk space. The notice will typically suggest that I need at least 1GB of free disk space. When I check the properties of my drive the free space is down to 1.2GB – 2GB of free space, which is sorta confusing because the notice says that if I have at least 1GB of free space I’m good.
At this point I go through my system cleaning/removing all temp files and folders and generally recover 2GB - 3GB of free disk space. Then I shut down and restart Logos. The reindex function then starts and completes its cycle. When I later check the properties of my drive I’m back up to my normal 11GB – 12GB of free disk space.
So it seems, as I’ve suggested, that Logo’s file structure or file management is very inefficient or at the very least very messy as it manages its files. What is the system doing that it chews up at least 10GB of disk space during its normal operation? Anybody else notice something like this?
James Thompson
Surface Laptop
Core i5, 8GB Ram, 117GB Disk