Bug 98860 - Dump doesn't support 32-bit UIDs
Summary: Dump doesn't support 32-bit UIDs
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: dump   
(Show other bugs)
Version: 9
Hardware: All Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-09 16:49 UTC by Steve Atwell
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version: 0.4b33
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-20 12:37:09 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 Steve Atwell 2003-07-09 16:49:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4b) Gecko/20030529
Mozilla Firebird/0.6

Description of problem:
If you dump and then restore files with 32-bit UIDs, the restored files will not
have the appropriate ownership.

This is fixed the current version of dump released by Stelian Pop, which is
version 0.4b34.

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

How reproducible:

Steps to Reproduce:
1. Create a file and chown 10000000:10000000 that file
2. Run "dump 0f /tmp/test.dump file"
3. Restore the dump

Actual Results:  The restored file will be owned by 38528:38528

Expected Results:  The file should be owned by 10000000:10000000

Additional info:

Comment 1 Mike A. Harris 2003-07-10 12:45:22 UTC
0.4b34 does not compile on all architectures supported by Red Hat currently.
In particular it fails on AMD64, ia64 at least, and possibly other 64bit

Once dump compiles on x86/ia64/AMD64/ppc/ppc64/s390/s390x again, I'll update
to the latest version though, but it's low priority as dump is a priority
3 package.  If this gets fixed upstream, it would expediate it getting updated
in the distribution however.

Comment 2 Mike A. Harris 2003-07-20 12:37:09 UTC
dump-0.4b33 in rawhide contains the fix for this problem.

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