Can I use reindex to re-index the entire filesystem? I’ve tried doing it, but pretty sure it’s not working. What I really need is an example of it in usage to re-index everything. Everything I can find shows what to do, but no actual examples.
The reason is that I want to periodically update our Tunetracker system to the latest Haiku betas and other other updates, but when I do that, Tunetracker’s “MakeMyDay” app which generates new playlists fails because it can’t find files with specific extended Attributes like Genre, Comment, etc. All the files are still in the folders and all the extended Attributes are there, it’s just that MakeMyDay can no longer “see” the Attributes. I would love to be able to do updates without crippling Tunetracker.
Not something I have ever done, but it seems you would do: reindex -r 'Media:Genre' '/path/under/which/the/files/are'
to reindex attribute Media:Genre for all files under /path/under/which/the/files/are, and you can use * to match a group of attributes.
Try it with the -v flag and just one file to see if it is doing something or not.
There’s also the question of why a reindexing would be needed. How are you updating? Unless you are formatting the device, or in some other way starting anew, I don’t expect the old indices to disappear during an update.
checkfs actually has code to re-index everything, but it’s only run if some very specific kinds of errors are detected inside the indices (which basically never seems to happen). I’ve hacked up builds before to force it to re-index everything and it works fine, much more efficiently than reindex; it might be worth adding some more flags to checkfs to force the use of this.
But as madmax notes, updating an existing install should not require indexes to be re-created, they aren’t destroyed by the updates. Can you try running some of the queries manually (via the query command line tool and see what happens?