At 5:14 PM +0530 11/17/06, pritam ghanghas wrote: >On Wed, 2006-11-15 at 19:29 -0500, Tony Nelson wrote: >> At 6:53 PM -0500 11/15/06, Sam Varshavchik wrote: >> >Content-Type: multipart/signed; >> > boundary="=_mimegpg-commodore.email-scan.com-28222-1163634835-0005"; >> > micalg=pgp-sha1; protocol="application/pgp-signature" >> > >> >Tony Nelson writes: >> > >> >> Is there a way to check the RPM database for validity? I know how to >> >> rebuild it, and where it is stored, and that when yum says that the >> >> database is corrupt that I must do something about it, but is there a way >> >> to test it before total failure? >> > >> >Well, "rpm -q -a -V" is going to go and read pretty much all the bits in the >> >rpm database. If something's busted, you're likely going to hit it. >> >> rpm -Va checks the possibly corrupt database's opinion of the filesystem, >> and may be considered a check on the database's accuracy. If RPM doesn't >> crash while doing it, nothing much is proved about its validity. >> >> Is there a tool or command to check the RPM database for being corrupt? >> -- >> ____________________________________________________________________ >> TonyN.:' The Great Writ <mailto:tonynelson@xxxxxxxxxxxxxxxxx> >> ' is no more. <http://www.georgeanelson.com/> > >There are a lot of tools in /usr/lib/rpm/ >they are supposed to be called by passing various options to rpm itself. >But you can use them directly as well. In your case you could use >/usr/lib/rpm/rpmdb_verify >you have to give this command the name of the db file to verify. Seems promising, especially as I don't know of a way to get rpm to verify its database rather than its packages. I used (all on one line): []# cd /var/lib/rpm ; for name in * ; do echo $name ; /usr/lib/rpm/rpmdb_verify $name ; done If there are lock files there (__db*) it won't like them. It also didn't like my Dirnames file. As the Packages file was OK, I used the "rpm --rebuilddb" command to fix it. I'm surprised that the database was corrupt, as it was rebuilt just before upgrading FC5 to FC6. I'll have to keep watching this. I also found a page on fixing RPM database problems on RHEL3 <http://people.redhat.com/berrange/notes/rpmrecovery.html>. I did make sure that there were no users of the RPM database before mucking about with it. -- ____________________________________________________________________ TonyN.:' The Great Writ <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' is no more. <http://www.georgeanelson.com/>
