The second question is: Since one of those Hfs+ partitions is my Time
Machine backup, and as I understand it, Spotlight and Time Machine go
hand-in-hand, can that index be rebuilt without having to wipe and
restart my time machine?
I don't know what you mean by hand in hand as these are entirely
separate functions. You probably do not want your time machine drive
indexed by spotlight in any event, so you may wish to exclude that
drive from being indexed.
I thought that Time Machine required, and depended on, spotlight.
My logs are constantly full of Time machine and spotlight
interactions, from bulk settings, to waiting for indexing, to issues
with backups failing because of indexing problems (and oddly, the next
backup will work just fine), etc.
The third observation/question: One of those Fat32 partitions has
several sparse bundles, each of which is an Hfs+ image. One gets
copies of everything that happens on a Windows XP machine; one
provides a Time Machine backup for that. Neither of them will ever
mount cleanly without an fsck_hfs running. Neither of them every say
why fsck has to run -- nothing shows up in the log. Is this just a
consequence of the drive holding the sparsebundle having a damaged
index, or is this an indication that those also need to be wiped and
start fresh?
This is a guess, but how large are those files? Fat32 has a hard
limit of 4GB for any single file. It's possible you're running into
that limit and your data is not being cleanly written to the sparse
bundles, resulting in file system corruption within them.
The nice thing about sparsebundles: There's nothing bigger than 8 MB
in any file, just a whole lot of them.
Or you might have a hardware problem. Check the entire drive for bad
blocks and then run diskwarrior/fsck/your favorite repair utility on
all file systems.
A "cat" of the drive showed no read errors. Fsck doesn't show any
issues.
Not the best test, but it's all I have at the moment.
Oh: Finder did another run-away. Spotlight is happy / indexes are ok.
Tomorrow I'll track down which partition is causing this.
Michael
---
PGP/GPG accepted; key 25D85CE0
Political and economic blog of a strict constitutionalist
http://StrictConstitution.BlogSpot.com
_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk
