Bug 460563 - "rpm --dump" shows size=0
"rpm --dump" shows size=0
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rpm (Show other bugs)
5.2
All Linux
low Severity low
: rc
: ---
Assigned To: packaging-team-maint
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-28 12:49 EDT by Petr Sklenar
Modified: 2013-03-07 04:45 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-07 04:45:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Sklenar 2008-08-28 12:49:38 EDT
Description of problem:
if file has size=1 then second field of "rpm --dump" shows size=0

priority = lower then low

Version-Release number of selected component (if applicable):
all
# rpm -q rpm
rpm-4.4.2.3-3.el5


How reproducible:
always

Steps to Reproduce:

# rpm -ql rpm --dump | grep __db.001
/var/lib/rpm/__db.001 0 1194852312 d41d8cd98f00b204e9800998ecf8427e 0100644 rpm rpm 1 0 0 X
# ll /var/lib/rpm/__db.001
-rw-r--r-- 1 root root 24576 2008-08-28 18:39 /var/lib/rpm/__db.001

  
Actual results:
--dump shows size of /var/lib/rpm/__db.001 zero

Expected results:
--dump shows size of /var/lib/rpm/__db.001 is 1

# rpm -ql rpm --dump | grep __db.001
/var/lib/rpm/__db.001 1 1194852312 d41d8cd98f00b204e9800998ecf8427e 0100644 rpm rpm 1 0 0 X

Additional info:

found during testing bug 250207
Comment 1 Panu Matilainen 2013-03-07 04:45:50 EST
/var/lib/rpm/* files are %ghost files, ie they are not created by installing the package. The size recorded in headers for %ghosts depends on what was present at build time, typically they are zero-length files created by running "touch", which is the case here. And as 'rpm -ql' shows the file data from headers, not filesystems, zero size is what you get. So this is not actually a bug but expected behavior for %ghost files.

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