Bug 21273 - cannot dump fs other than /
cannot dump fs other than /
Status: CLOSED DUPLICATE of bug 21272
Product: Red Hat Linux
Classification: Retired
Component: dump (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Dale Lovelace
Depends On:
  Show dependency treegraph
Reported: 2000-11-22 22:15 EST by ae
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-11-22 22:15:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description ae 2000-11-22 22:15:47 EST
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 00:31:06 EST

*** This bug has been marked as a duplicate of 21272 ***

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