On 2009/11/19 23:26 (GMT-0700) Michal Jaegermann composed:
Felix Miata wrote:
I went to tty2 and did rpm --rebuilddb, but that apparently accomplished nothing other than this output:
error: failed to replace old database with new database! error: replace files in /var/lib/rom with files from /var/lib/rpmrebuildb.1206 to recovererror: failed to remove directory /var/lib/rpmrebuilddb.1206: Directory not empty
That is quite far from "nothing". In /var/lib/rpmrebuilddb.<something> you have all new database files and this replacement where you got an error is a penultimate step in a --rebuilddb process. Sounds like a new database was already made. A removal of build directory failed because files from there were not moved to their targets.
Hence the questions are:
- are you out of a disk space?
no
- did you remove /var/lib/rpm/_* lock files before trying rebuild?
forgot
- did something put funky attributes on files in /var/log/rpm?
not likely
- is your file system which holds /var/lib/rpm healthy?
It was right before I started Anaconda, but I wasn't paying attention of first reboot after and am thus unsure whether Anaconda left it corrupted.
'man lsattr' describes how to list attributes and 'man chattr' explains their meanings but run fsck first.
By the time I saw this reply I had already started installation all over again. While waiting for a reply I remembered https://qa.mandriva.com/show_bug.cgi?id=32547 and suspected the workaround for that bug (/ and/or /var/lib/rpm ext3 filesystem blocksize != 1024) might apply here. Instead of actually applying that workaround, I instead elected to do a minimalist install (no X, no OO.org, etc) of considerably fewer packages (~640) as on the first try (>1200), which worked.