4.5b Beta 7: Indexer reports "insufficient free disk space" when plenty of space

I ran "rebuild index" (to test whether some other bug had been fixed).

I got this error message:

It turns out I was indeed low on disk space on my C: drive (though not on my second hard drive, where I have over 800GB free).

So I deleted all my browser history, and that cleared up 100GB!!

Before:

After:

Next, I restarted Logos and the indexer began again. It stopped again and claimed to be out of disk space again (same error message box). But this time, that was patently not true, as demonstrated by the second disk space screenshot above.

Log files from the first time the indexer pooped out: 8321.IndexerStopped20120421.zip

Log files from the second time the indexer pooped out: 1488.IndexerStopped20120422.zip

Interestingly, the second try, after I'd cleared up gobs of disk space, it got through indexing only "786 of 9,190 resources" before failure. The first time, it got through "4,179 of 9,190 resources."

If the failure of the indexer the first time left things in such a state that caused the failure to occur the second time, then the indexer needs to be better about cleaning up after itself in a failure case.

NOTE: I see someone else reported this problem before (and another one chimed in that he's gotten that error when unwarranted too). But nobody from Logos ever responded to that thread, and there weren't sufficient log files uploaded to track it down anyway:

http://community.logos.com/forums/t/38351.aspx

Find more posts tagged with

Comments

Bradley Grainger (Logos)

The logs do indicate that the indexer ran out of disk space, but don't indicate any more detail, unfortunately. I'm adding a little more logging for the next release.

Is it at all possible that some other program temporarily reduced free disk space to <1GB while the indexer was running?

Rosie Perera

https://community.logos.com/discussion/comment/361692#Comment_361692

The logs do indicate that the indexer ran out of disk space, but don't indicate any more detail, unfortunately. I'm adding a little more logging for the next release.

Is it at all possible that some other program temporarily reduced free disk space to <1GB while the indexer was running?

Not remotely possible. I had nothing else out of the ordinary running, and 100GB of free disk space. The only thing might be if the disk space I freed up by deleting all my browsing history was not actually available yet. But I don't see how that could be. I tried re-indexing again before rebooting the machine and it worked the third time.

JT (alabama24)

https://community.logos.com/discussion/comment/361738#Comment_361738

100GB of free disk space

Not nearly enough. [:P]

Dave Hooton

https://community.logos.com/discussion/comment/361750#Comment_361750

100GB of free disk space

Not nearly enough.

The interesting part was that browser history was 100 GB!!

Rosie Perera

https://community.logos.com/discussion/comment/361807#Comment_361807

100GB of free disk space

Not nearly enough.

The interesting part was that browser history was 100 GB!!

I had not cleared it since I bought my machine. But that's a pretty surprisingly large amount of browser history, even with all the time I spend online. I wonder if movies streamed (e.g., from Netflix) are downloaded in temp files there? That would be the only way I could imagine filling up so many GB of data.

Dave Hooton

https://community.logos.com/discussion/comment/361889#Comment_361889

I wonder if movies streamed (e.g., from Netflix) are downloaded in temp files there?

Quite likely. You might also check C:\Users\Username\Downloads.