Hi, I've just been setting up a couple of new PowerBooks (1.67GHz), and after configuring everything for the user, I decided to run Indexing on the hard drive. I selected the Macintosh HD, selected Get Info, then Content Index, and Index Now. The Indexing starts and seems to be working fine as it chugs through 25,000 files or so. Then, it appears to finish, but the Content Index field then says, once again, NOT INDEXED.
If I try to immediately run the Indexing again, it will run a few seconds then quit with the same message, NOT INDEXED. If I go into the ~/Library/Indexes/FindByContent folder and delete its contents, I can successfully restart the Indexing process. Now, if I periodically stop it, say after 20,000 files or so, it will stop, say the drive is Indexed, and appear to be finished. I can then rerun Indexing, it will zip through the previously created partial Index and continue on.
Here's the issue. If I let the Indexing continue to run, updating the previously partially Indexed file, it will continue, but get to a point where it stops, and then again returns the NOT INDEXED message. If I go back into the directory, the recently created Index is there (typically 25MB or so), but the Indexing utility is no longer accessing it. If I attempt to run Indexing again, it will create a new folder (00002) and start creating a new Index.
So, my question is, is this normal behavior now in 10.3.9? Previously, I could rerun the Indexing at any time, and it would just update the previously created Index file. Now, unless I force the Indexing to stop mid-way through the process to get it to report the drive Indexed, it will continue until it stops and report the drive is not Indexed.
Does anyone have any idea exactly how this indexing is supposed to work in 10.3.9? It would seem to me that if the Get Info thinks the drive is not Indexed, then the System wouldn't look to that file to use it in searches. However, if I stop the Indexing prematurely so that it returns an Indexed message, that the System would then be able to use it. Comments?
If I try to immediately run the Indexing again, it will run a few seconds then quit with the same message, NOT INDEXED. If I go into the ~/Library/Indexes/FindByContent folder and delete its contents, I can successfully restart the Indexing process. Now, if I periodically stop it, say after 20,000 files or so, it will stop, say the drive is Indexed, and appear to be finished. I can then rerun Indexing, it will zip through the previously created partial Index and continue on.
Here's the issue. If I let the Indexing continue to run, updating the previously partially Indexed file, it will continue, but get to a point where it stops, and then again returns the NOT INDEXED message. If I go back into the directory, the recently created Index is there (typically 25MB or so), but the Indexing utility is no longer accessing it. If I attempt to run Indexing again, it will create a new folder (00002) and start creating a new Index.
So, my question is, is this normal behavior now in 10.3.9? Previously, I could rerun the Indexing at any time, and it would just update the previously created Index file. Now, unless I force the Indexing to stop mid-way through the process to get it to report the drive Indexed, it will continue until it stops and report the drive is not Indexed.
Does anyone have any idea exactly how this indexing is supposed to work in 10.3.9? It would seem to me that if the Get Info thinks the drive is not Indexed, then the System wouldn't look to that file to use it in searches. However, if I stop the Indexing prematurely so that it returns an Indexed message, that the System would then be able to use it. Comments?