From owner-freebsd-stable Mon Oct 19 08:04:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13846 for freebsd-stable-outgoing; Mon, 19 Oct 1998 08:04:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13840 for ; Mon, 19 Oct 1998 08:04:22 -0700 (PDT) (envelope-from benst@nemesis.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9891-23405>; Mon, 19 Oct 1998 17:03:44 +0200 Received: from nemesis.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.9.1) with UUCP id QAA07080 for stable@freebsd.org; Mon, 19 Oct 1998 16:59:06 +0200 (MET DST) (envelope-from benst@nemesis.stuyts.nl) Received: from giskard.stuyts.nl (giskard.stuyts.nl [193.78.231.1]) by nemesis.stuyts.nl (8.8.8/8.8.8) with ESMTP id QAA04173 for ; Mon, 19 Oct 1998 16:41:06 +0200 (CEST) (envelope-from benst) Received: (from benst@localhost) by giskard.stuyts.nl (8.8.5/8.8.5) id QAA16098 for stable@freebsd.org; Mon, 19 Oct 1998 16:41:05 +0200 (MET DST) Message-Id: <199810191441.QAA16098@giskard.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Mon, 19 Oct 98 16:41:03 +0200 To: stable@FreeBSD.ORG Subject: int overflow in tar Reply-To: ben@stuyts.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, The gnu tar program included with FreeBSD has a tiny problem with the option --totals. This option prints the total number of bytes written, but unfortunately the counter used by tar (tot_written in tar.h) is an int. So it overflows after 2^31 bytes have been written, like this: Backing up nemesis:/home3 at Mon Oct 19 13:27:43 CEST 1998 ... Total bytes written: -1960021504 df /home3 shows: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd2s1f 3857506 2307663 1241243 65% /home3 Should I take this up with the people who maintain gnu tar, or is this something we can fix in our source tree? Could there be more int overflow problems with tar? Best regards, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message