Bug 57851 - rpm stops working permanently when disk space is temporarily exhausted
Summary: rpm stops working permanently when disk space is temporarily exhausted
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
(Show other bugs)
Version: 7.2
Hardware: All Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-12-28 07:07 UTC by izv
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-12-28 07:07:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description izv 2001-12-28 07:07:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.2-15mdk i686)

Description of problem:
all rpm operations (including simple ones like rpm -q package) fail after
disk space is exhausted.  the problem continues even when more disk space
is available later.

removing a file /var/lib/rpm/__db.001 (zero size, presumably libdb temp
file) fixes the problem.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. fill up disk containing /var/lib/rpm so that there is no space remaining
2. run rpm -qa (it fails with an error message)
3. free up some disk space
4. run rpm -qa (it still fails with an error message, see below)

Actual Results:  rpmdb: unable to join the environment
error: db3 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index using db3 - Resource temporarily
unavailable (11)

Expected Results:  rpm prints out list of packages

Additional info:

removing the file /var/lib/rpm/__db.001 (zero size, presumably libdb temp
file) fixes the problem

Comment 1 Jeff Johnson 2001-12-28 17:04:01 UTC
	rm -f /var/lib/rpm/__db*
	rpm --rebuilddb
Please reopen this bug if the above does not fix.

Note You need to log in before you can comment on or make changes to this bug.