maybe yum-updatesd? (was Re: yum updates corrupting rpmdb)

Joe Smith jes at martnet.com
Sat Jan 5 06:07:36 UTC 2008


Joe Smith wrote:
> ...
> I'm running a "rpm -Va" just now, and so far it looks reasonable, so 
> maybe the problem is done now.
> ...

Nope. Yum can even successfully finish an update which apparently leaves 
errors in the database:

# yum update
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package gnupg2.i386 0:2.0.8-1.fc8 set to be updated
---> Package gdb.i386 0:6.6-39.fc8 set to be updated
---> Package liferea.i386 0:1.4.10-1.fc8 set to be updated
---> Package libEMF.i386 0:1.0.3-5.fc8 set to be updated
---> Package yum-utils.noarch 0:1.1.9-2.fc8 set to be updated
---> Package libcdio.i386 0:0.78.2-4.fc8 set to be updated
--> Finished Dependency Resolution
   ...
Updated: gdb.i386 0:6.6-39.fc8 gnupg2.i386 0:2.0.8-1.fc8 libEMF.i386 
0:1.0.3-5.fc8 libcdio.i386 0:0.78.2-4.fc8 liferea.i386 0:1.4.10-1.fc8 
yum-utils.noarch 0:1.1.9-2.fc8
Complete!
# cd /var/lib/rpm
# for f in `ls | grep -v '\.'`; do /usr/lib/rpm/rpmdb_verify $f; done
db_verify: Page 2355: partially zeroed page
db_verify: Dirnames: DB_VERIFY_BAD: Database verification failed
db_verify: Page 641: bad page number 247
db_verify: Providename: DB_VERIFY_BAD: Database verification failed
db_verify: Page 109: partially zeroed page
db_verify: Provideversion: DB_VERIFY_BAD: Database verification failed
db_verify: Page 247: partially zeroed page
db_verify: Requireversion: DB_VERIFY_BAD: Database verification failed
db_verify: Page 160: bad page number 109
db_verify: Sha1header: DB_VERIFY_BAD: Database verification failed

If it hadn't ever worked, I'd be looking at hardware, but it's worked 
well for many months (f7/8), and I'm seeing no drive errors or 
instability otherwise.

<Joe




More information about the fedora-list mailing list