At 7:53 PM -0500 11/19/06, Jim Cornette wrote: >Thanks for the link regarding the hidden option to rpm which verifies >database integrity. I was bit while trying to install via yum the >ntfs-sg3 package. The below output was reported. > >Symptom: segmentation fault when installing ntfs read/write package. >Trying to run rpm --rebuilddb stays in locked condition and does not >proceed further. > >There is a problem. What do you suppose it is? >Jim > > rpm --verifydb ... >rpmdb: /var/lib/rpm/Requirename: DB_VERIFY_BAD: Database verification failed ... >rpmdb: /var/lib/rpm/Basenames: DB_VERIFY_BAD: Database verification failed ... >rpmdb: /var/lib/rpm/Packages: DB_VERIFY_BAD: Database verification failed Well, your RPM database is pretty well hosed. The --rebuilddb option fails because it uses Packages, which is damaged. This RHEL3 page <http://people.redhat.com/berrange/notes/rpmrecovery.html> has suggestions for what to try, such as dumping the Packages file and re-importing it (some lossage will occur). Using --initdb will remove any chance of --rebuilddb working, so don't until you are moving on to other methods. Per Matthew Saltzman on 20 Oct 2005 17:01:42 "Re: RPM Database broken", /var/log/rpmpkgs* lists the RPMs on your system (yesterday); you can download all of them (eww -- possibly just the headers?) and use "rpm -U --justdb <filename>" on them (frm a script). Finish up by hand. Yum may have its own separate opinion of what's installed? When you finish, run "package-cleanup --problems" from yum-utils, and "rpm -Va". -- ____________________________________________________________________ TonyN.:' The Great Writ <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' is no more. <http://www.georgeanelson.com/>
