Bug 21253

Summary: dump/restore fail on any stream (tape/pipe/file) over 4GB
Product: Base System Reporter: bigfoot <bigfoot>
Component: binAssignee: Matt Jacob <mjacob>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description bigfoot 2000-09-13 20:30:00 UTC 
dump/restore incorrectly assumes any restore stream longer than 4GB spans another tape.

[7:11am] 102 [/titan5]:titan% ls -l /titan1
total 24617616
-rw-r-----  1 root  wheel  1124892672 Sep 12 21:13
www.stomped.com._usr_local_webs.20000710.4
[7:11am] 103 [/titan5]:titan% restore x -f
/titan1/www.stomped.com._usr_local_webs.20000710.4
Comment 1 dwmalone 2000-09-13 22:36:43 UTC 
On Wed, Sep 13, 2000 at 12:27:14PM -0700, bigfoot@stomped.com wrote:

> [7:11am] 103 [/titan5]:titan% restore x -f
> /titan1/www.stomped.com._usr_local_webs.20000710.4

I think this works if you read from stdin:

	restore xf - < /titan1/www.stomped.com._usr_local_webs.20000710.4

There are other ways to do this too, but this is one easy way.

	David.
Comment 2 dwmalone 2000-09-17 21:59:02 UTC 
> I went and checked this also. Restore has no problems
> reading 8GB from standard input. It sounds like the only
> thing could be is something destroying the pipe.

I can't reproduce it either just by trying to restore a large
filesystem:

15:43:walton 4# restore xf - < ../src-dump
restore xf - < ../src-dump
set owner/mode for '.'? [yn] n
21:50:walton 5# fg
21:50:walton 6# ls -l ../src-dump
-rw-------  1 root  wheel  3211929600 Sep 17 11:38 ../src-dump

Whatever the problem is, it doesn't seem to be restore. Maybe
they're somehow producing bad dump files?

	David.
Comment 3 mjacob 2000-10-29 18:28:24 UTC 
I don't believe we can reproduce this. I believe this should be closed.
Comment 4 iedowse freebsd_committer freebsd_triage 2001-08-13 00:39:08 UTC 
State Changed
From-To: open->feedback


Can this be closed?
Comment 5 Matt Jacob freebsd_committer freebsd_triage 2001-10-02 03:02:44 UTC 
Responsible Changed
From-To: freebsd-bugs->mjacob

I might as well look at this. 
.
Comment 6 iedowse freebsd_committer freebsd_triage 2002-03-01 21:33:54 UTC 
State Changed
From-To: feedback->closed


Feedback timeout, and the problem (which was probably triggered by 
dumping an active filesystem) is believed to be fixed by some 
recent restore(8) changes.