Originally posted by Marvin
Does it really damage the drive structure if you leave it? I think there is still a machine I need to fix at work but I haven't gotten round to it.
Well, I posted various concerns about a problem that I encountered, a few months ago. Basically, Spotlight would keep re-indexing my drives (as though it was the first time that it had seen the drives in question).
The crux of the problem was that it appeared as though "something" had "downsized" the drives and the displaced data either vanished or became corrupted.
My understanding is that if the volume header becomes corrupted to the point where the reported size of the drive starts changing, Spotlight might indeed believe that it is seeing a new drive for the first time an then proceed to re-index said drive.
This problem was unfortunately repeatable (I decomissioned a G5 that I believed was "jinxed" as after several nuke & pave installs on different hard disk mechansims the problem kept reoccuring, only to replace the G5 with another machine which suffered the same problem).
The more I learn about this CS2 problem, and the effects it has on the volume header, the more convinced I become that CS2 is the "something" that caused all the problems.
If I were you, I wouldn't wait to see just how bad it can get!