Bug 17791

Summary: Restore does not handle bad or missing tapes well.
Product: Base System Reporter: cjohnson <cjohnson>
Component: binAssignee: iedowse
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-RELEASE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description cjohnson 2000-04-04 18:10:01 UTC
Did full back up of 5GBytes of data onto 4 tapes using dump.
First two tapes are full with no errors.  3rd tape had IO error shortly
into writing.  Dump then asked for 4th tape and completed the dump to that
tape.

On restoring this data, when restore found the IO error on tape 3 it 
did not allow a method for moving on.  Selecting "continue" caused it to
retry over and over again.  Never moving past the error, never generating
an ENOSPACE (End of Tape) error.  When the question is answered "no" the
restore ends.

restore -Rf /dev/rsa0 demanded tape 3 again, it wouldn't let me put tape
4 into the drive.  Modifying /usr/src/sbin/restore/tape.c to make
'R' ask the user for the tape volume number.  This allowed me to move on
to the last tape which then told me about lots of missing files (Lost
on the dump or restore?)  Finally it read the last of tape four and ended
WITHOUT SETTING OWNERS OF PERMISSIONS!

Fix: Well, this will get the data in but I don't like it at all.

RCS file: /usr/cvsroot/src/sbin/restore/tape.c,v
retrieving revision 1.16
How-To-Repeat: 
see description.
Comment 1 cjohnson 2000-04-05 14:19:15 UTC
As pointed out to me by a very nice person, to get the permissions of
the
directories reset correctly you load the first tape and do:

    restore -if /dev/rsa0
    add
    setmodes
    quit
Comment 2 Matt Jacob freebsd_committer freebsd_triage 2000-10-29 18:41:05 UTC
Class Changed
From-To: sw-bug->change-request

This is a change request.
Comment 3 Matt Jacob freebsd_committer freebsd_triage 2001-10-02 02:58:51 UTC
Responsible Changed
From-To: freebsd-bugs->mjacob

I might as well eventually look at this one. 
.
Comment 4 iedowse freebsd_committer freebsd_triage 2002-03-01 21:37:03 UTC
State Changed
From-To: open->closed


This has been fixed in both -CURRENT and -STABLE; restore's handling 
of multi-volume dumps had a lot of bugs, most of which are hopefully 
now fixed. To get the fixed version you will need to either cvsup 
to -STABLE, or wait for 4.6-RELEASE. 


Comment 5 iedowse freebsd_committer freebsd_triage 2002-03-01 21:37:03 UTC
Class Changed
From-To: change-request->sw-bug

This really was a bug. 


Comment 6 iedowse freebsd_committer freebsd_triage 2002-03-01 21:37:03 UTC
Responsible Changed
From-To: mjacob->iedowse

I'm interested in any followups.