Testing /var/db/pkg/database integrity

[TheLexx]

Is there a way to test the /var/db/pkg/ database integrity?

Being am "old-schooler" I have /var on a separate filesystem from /usr. When I tried using some portage commands. I got some complaints, something like "Invalid db entry", but I don't remember the exact wording.

From Finnix, I used fsck and found out that there were flaws in some of my filesystems. I then was able to use fsck & smartctrl to correct the problem and test the drive. I had problems inside both the /usr/portage and /var/db/pkg/ directories. Although the damage inside /usr/portage was much greater. I found it simpler to just delete the portage dir and reinstall from a portage snapshot. Now that I have fixed the effected filesystems, I can use commands like "emerge --pretend evolution" and "equery files wireshark" without error. I am still concerned that there could still be errors within the /var/db/pkg/ database that could turn up while doing later upgrades. Is there a way to test the entire database for bad entries?

[VinzC]

Being old-school as well as having very little knowledge of portage internals, I'd emerge -e world using saved binary packages if you have any. Otherwise you might attempt to reconstruct your db/pkg directory tree. I have seen there are some scripts around for a couple of years but I guess the recent versions of portage do include such "medical" assistance.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!