>Number:         32105
>Category:       bin
>Synopsis:       gzip exits with non-zero status for >=4GB input.
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 18 12:50:00 +0000 2005
>Originator:     Atsushi Onoe
>Release:        NetBSD 3.99.11
>Organization:
>Environment:
System: NetBSD nebula.sm.sony.co.jp 3.99.11 NetBSD 3.99.11 (NEBULA) #53: Sun Nov 13 11:10:31 JST 2005 onoe@nebula.sm.sony.co.jp:/usr/obj/NEBULA i386
Architecture: i386
Machine: i386
>Description:
	Because of recent changes (28 August, rev 1.73 of gzip.c),
	a dump script like
		dump 0f - /home | gzip > home.dump.tmp.gz &&
		    mv home.dump.tmp.gz home.dump.gz
	always fails when the partition has over 4GB content.
	Note that testing the status of gzip is to catch the file system
	full case.

	It says "input file size >= 4GB cannot be saved" and exit(1).
	But gzip does not loose any data, and the result can be
	fully restored.  For over 4GB input, only "gzip -l" would fail.

	For compatibility of scripts written before, and interoperability
	of gnu-gzip, it should not claims for >=4GB input and should
	exit with 0, IMHO.

>How-To-Repeat:
>Fix: