bin/86690: bsdtar sparse file problems

Juergen Lock nox at jelal.kn-bremen.de
Wed Sep 28 14:30:22 PDT 2005


>Number:         86690
>Category:       bin
>Synopsis:       bsdtar sparse file problems
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Sep 28 21:30:21 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Juergen Lock
>Release:        FreeBSD 5.3-RELEASE-p20 i386
>Organization:
me?  organized??
>Environment:
System: FreeBSD saturn 5.3-RELEASE-p20 FreeBSD 5.3-RELEASE-p20 #1: Fri Jul 29 14:59:03 CEST 2005 nox at saturn:/usr/home/nox/src5/usr/src/sys/i386/compile/NEPTUN i386


>Description:

If i create an empty 5G sparse file,

-rw-r--r--  1 nox  wheel  5368709120 Sep 28 23:05 sparse

and archive it with gtar (result uuencoded below), then gtar tfvz
lists it correctly as:
-rw-r--r-- nox/wheel 5368709120 Sep 28 23:05 2005 sparse

but bsdtar lists it as:
?rw-r--r--  0 nox    wheel 1073741824 Sep 28  23:05 sparse

(btw what does the ? stand for?), and extracts it to a 1 byte file.
And even if its not empty (e.g. install 4.11 into it using it as a
raw qemu disk image), bsdtar lists it with the wrong size.

begin 644 sparse.gtar.gz
M'XL(`)T%.T,``^W000J#,!"%X1PE1WBQ<3Q(3^`BT$51,99Z_!I*6[IQ97#S
M?YL'PV,8)D_]G).K2D&R&)VDT+4J67RRC%W0)9BI,=G6C\T6_EKWK+='7OK9
M>S>,ZV[O>4OI7N.`V'W]?>0P[6_K<4L!`````````````````.=Z`7>9++D`
#*```
`
end

>How-To-Repeat:
	see above
>Fix:

	
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list