I recently upgraded from 8.0 to 8.2 on a P3-733 machine running an
Acer MB (M25D, I think). After a week or so, and without being certain
of the exact sequence of events leading up to this, the RPM database
seems to have become corrupted.
'rpm -q --all' lists 537 packages, ending with an old
'kernel-2.4.3-20mdk', then gets a SEGV and core dumps. Notably, I had
been trying to 'rpm -e' this package at about the same time that I first
noticed the corruption. There were more than 537 packages installed, as
well.
'rpm --rebuilddb' cranks away for a while, then also gets a SEGV and
core dumps, leaving about 18 MB of stuff behind in
/var/lib/rpmrebuilddb.<pid>
Both errors are repeatable. It's possible that the sequence of events
leading up to this was something like:
- Upgrade to 8.2
- Install and remove various additional packages (notably, removing
some old packages from 8.1 and 8.2 Cookers).
- At some point, fill up the partition containing /var/lib, without
noticing it.
- Attempt to rpm -e kernel-2.4.3-20mdk and kernel-source-2.4.3-20mdk.
- Notice RPM DB corruption.
However, I'm not particularly confident in stating this was the
actual sequence of events.
Is this known behavior? Do I have any options other than a clean
re-install of 8.2? Searching through old archives of the expert list, I
came across a pointer to Pascal Bourguignon's howto on rebuilding the DB:
http://hermes.afaa.asso.fr/users/pascal/linux/rpm-rebuilddb
I'm willing to give this a try if there's a good chance of success,
though I'd first like to hear if anyone else has dealt successfully with
this problem.
Thanks,
Jon Leech
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
