This applies to POPFile 0.20.x only. It may be be helpful if you are having trouble upgrading from 0.20.x. The problems described no longer affect the current version of POPFile.
The unsupported dbverify utility will check your corpus for corruption. It peforms the following checks;
You can be reasonably assured that your table.db files are not corrupt if the utility fails to report any errors.
cd "\program files\popfile"
perl dbverify.pl
Note: If you have changed the default location of your corpus via the bayes_corpus parameter, you must pass the new corpus directory location to the utility on the command line (most users can ignore this note, only advanced users would have made this particular change).
In this example, the utility is shown reporting corruption in both the magnet and spam buckets for this corpus.
Checking corpus/magnet/table.db *ERROR** bucket corpus/magnet has a corrupt corpus, db_verify returns: DB_VERIFY_BAD: Database verification failed Bucket corpus/magnet is likely corrupt, word count is 6237 versus 5250 Bucket corpus/magnet is likely corrupt, unique count is 1767 versus 4308 Checking corpus/normal/table.db Checking corpus/spam/table.db *ERROR** bucket corpus/spam has a corrupt corpus, db_verify returns: DB_VERIFY_BAD: Database verification failed
In this example, the utility is shown reporting no instances of corruption in any of the three buckets of the corpus.
Checking corpus/magnet/table.db Checking corpus/normal/table.db Checking corpus/spam/table.db
Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.