On Thu, Nov 13, 2008 at 12:36 PM, <<a href="mailto:pmatilai@laiskiainen.org">pmatilai@laiskiainen.org</a>> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Sun, 5 Oct 2008, José Matos wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Saturday 04 October 2008 02:09:05 Antonio Olivares wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Dear fellow testers, I tried to use xterm but it was not installed, so I wanted to yum install it, and I got message in the title. [root@riohigh ~]# yum install xterm Loaded plugins: refresh-packagekit rpmdb: Thread/process 21524/3086247616 failed: Thread died in Berkeley DB library rpmdb: unable to allocate memory for mutex; resize mutex region error: cannot open Name index using db3 - Cannot allocate memory (12) rpmdb: unable to allocate memory for mutex; resize mutex region error: cannot open Providename index using db3 - Cannot allocate memory (12) rpmdb: Thread/process 21524/3086247616 failed: Thread died in Berkeley DB library </blockquote> rm -rf /var/lib/rpm/__db.* should allow you to continue. At least it does to me. :-) </blockquote> </div> Are you by any chance using ext4 as the filesystem? There seems to be a pattern developing here: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=468437" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=468437</a> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=471411" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=471411</a> </blockquote></div> Aha - ext4 root here as well. rpmdb corruption first started happening again for me on F9 around November 10th, and looking back at the yum.log an updates-testing kernel from a few days earlier Nov 07 08:49:30 Installed: kernel-2.6.27.4-26.fc9.x86_64 I've had to rm /var/lib/rpm/__* 4 times in the past few days to allow yum/rpm to continue.