Bug 21272

Summary: cannot dump fs other than /
Product: [Retired] Red Hat Linux Reporter: ae
Component: dumpAssignee: Mike A. Harris <mharris>
Status: CLOSED RAWHIDE QA Contact: Dale Lovelace <dale>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-04-25 19:33:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description ae 2000-11-23 03:15:47 UTC
cannot dump fs other than /


LIST="/var /"

for j in $LIST; do
	/sbin/dump 0bBuf 48 500000 /dev/nst0 $j

export TAPE=/dev/st0
mt rewind

/sbin/restore is 1
. is not on the tape
Root directory is not on tape
abort? [yn] n
/sbin/restore > ls
/sbin/restore > quit

[root@dogsbody /var]# /sbin/restore is 2
/sbin/restore > ls
.bash_history  dos            net            tmp--          u6 
bin            etc            opt            u1             u7 
boot           home           proc           u10            u8 
burner         info           roast          u11            u9 
cdrom          lib            root           u2             usr 
cdrom4         lost+found/    sbin           u3             var 
cdrom6         misc           tftpboot       u4 
dev            mnt            tmp            u5 

/sbin/restore > quit

Tested other way around; in thad case file 1 looks like my root,
and file 2 DOES NOT show anything.

[ maybe related, maybe independant. ]
Trouble with writing multiple tape files from Solaris client; can
see only the last in the set.  This worked OK a while ago.
Am using the no-implicit-rewind device /dev/nst0.


Comment 1 Bill Nottingham 2000-11-24 05:31:03 UTC
*** Bug 21273 has been marked as a duplicate of this bug. ***

Comment 2 Mike A. Harris 2001-11-22 04:03:16 UTC
Can you test dump 0.4b25 from rawhide?  It is believed that
this problem is now not reproduceable in this release.

Comment 3 Stelian Pop 2002-04-25 19:33:35 UTC
I think this bug could be closed now...

Comment 4 Mike A. Harris 2002-04-25 22:35:52 UTC