I have a large library (roughly 31 gig). My 500 gig hard disk (HD) was showing only 8 gig left (neither Dell or I could calculate more than 230 gig actually being used of a the 464 gig drive (after formatting)). Why the 234 gig discrepancy?
Logos 6 downloaded some more files, ran the indexing routine and suddenly I had 230 gig available on the HD!!! I wonder what the size of the index files run for a large library? Are they deleted when new indices are created? More important, are they hidden from the properties command of file explorer so that their size is not obvious to the casual user (I unhide all files on my Win 7 ultimate computer)? Where are these indices found on the HD? On the other hand, does the OS disk space remaining tally accurately reflect their presence? Dell and I are stumped and a programmer friend of mine at my synagogue strongly suspected that indexing scratch files could be the cause.
I am not accusing Logos indices of being the culprit, rather I am trying to gather information and eliminate possibilities. I fear that if the available space tally drops much less than 6 gig, the OS will be unable to write its scratch files and the system will grind to a halt or stall.