From nobody  Thu May  8 18:23:09 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA01131;
          Thu, 8 May 1997 18:23:09 -0700 (PDT)
Message-Id: <199705090123.SAA01131@hub.freebsd.org>
Date: Thu, 8 May 1997 18:23:09 -0700 (PDT)
From: aloke@vicor-nb.com
To: freebsd-gnats-submit@freebsd.org
Subject: the -L option of tar does not work properly with long tape lengths
X-Send-Pr-Version: www-1.0

>Number:         3552
>Category:       gnu
>Synopsis:       the -L option of tar does not work properly with long tape lengths
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May  8 18:30:01 PDT 1997
>Closed-Date:    Thu Aug 22 10:16:11 PDT 2002
>Last-Modified:  Thu Aug 22 10:16:11 PDT 2002
>Originator:     Aloke
>Release:        2.2.1-RELEASE
>Organization:
Vicor Inc.
>Environment:
FreeBSD soundy.vicor-nb.com 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE #0: Thu May  8 11:27:18  1997     aloke@soundy.vicor-nb.com:/usr/src/sys/compile/NEXUS  i386

>Description:
GNU tar version 1.11.2. The -L option to tar is supposed to specify the length of the tape in K,
but when the number is large (I was using 3145000 to specify a 3Gig tape)
the user is prompted to mount a second volume too soon. A look
at the source shows the tape_length variable to be a signed int, instead
of unsigned.
>How-To-Repeat:
tar -c -v -M -L 3145000 -f /dev/rst0 .
where "." is populated with some large files (in my case, 2 files
of 64 Meg and 44 Meg). tar will ask for the 2nd volume to be written
MUCH before having written 3gigs.
>Fix:
in /usr/src/gnu/usr.bin/tar/buffer.c changed 
"static long bytes_written = 0;" to "static unsigned long bytes_written = 0; "

in /usr/src/gnu/usr.bin/tar/tar.h changed
"TAR_EXTERN int tape_length;" to "TAR_EXTERN unsigned long tape_length;"
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: asmodai 
State-Changed-When: Sat Feb 5 04:20:26 PST 2000 
State-Changed-Why:  
tar 1.13 clears possibly all problems mentioned this 
this PR.  Now to find someone to upgrade it.  Guess I am the 
sucker for that. 
Responsible-Changed-From-To: freebsd-bugs->asmodai 
Responsible-Changed-By: johan 
Responsible-Changed-When: Fri Oct 27 13:15:24 PDT 2000 
Responsible-Changed-Why:  
Where you serious about upgrading tar to 1.13? 

If so please also have a look at all the other tar related PRs. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=3552 
Responsible-Changed-From-To: asmodai->freebsd-bugs 
Responsible-Changed-By: asmodai 
Responsible-Changed-When: Fri Nov 16 02:24:16 PST 2001 
Responsible-Changed-Why:  
Move back to the free pool. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3552 

From: Marc Perisa <perisa@porsche.de>
To: freebsd-gnats-submit@FreeBSD.org, mjacob@FreeBSD.org
Cc:  
Subject: Re: gnu/3552: the -L option of tar does not work properly with long
 tape lengths
Date: Wed, 29 May 2002 02:45:17 +0200

 Please close this PR. It is better described at
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/24903
 
 Thanks
 
 Marc
 
 
 

From: Marc Perisa <perisa@porsche.de>
To: mjacob@FreeBSD.org
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: gnu/3552: the -L option of tar does not work properly with long
 tape lengths
Date: Wed, 29 May 2002 02:46:25 +0200

 Marc Perisa wrote:
 
 > Please close this PR. It is better described at
 >
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/24903
 >
 > Thanks
 >
 > Marc
 >
 >
 Sorry,
 
 I mixed up the numbers - this one is already closed.
 
 Meant was http://www.freebsd.org/cgi/query-pr.cgi?pr=3552 (submitted 
 seperated feedback already)
 
 Thanks
 
 Marc
 
 
 
State-Changed-From-To: analyzed->patched 
State-Changed-By: sobomax 
State-Changed-When: Tue Jun 4 10:50:57 PDT 2002 
State-Changed-Why:  
Modern GNU tar which was just imported into the -CURRENT doesn't have this 
problem. Therefore, the problem will befilly resolved when tar upgrade is 
MFC'ed in about 1 month. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=3552 
State-Changed-From-To: patched->closed 
State-Changed-By: johan 
State-Changed-When: Thu Aug 22 10:14:33 PDT 2002 
State-Changed-Why:  
GNU tar 1.13.25 has been MFCed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=3552 
>Unformatted:
