From owner-freebsd-stable Tue May 14 20:14: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from violet.metron.com (indigo.metron.com [192.160.193.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C73037B400 for ; Tue, 14 May 2002 20:14:04 -0700 (PDT) Received: from violet.metron.com (localhost.metron.com [127.0.0.1]) by violet.metron.com (8.12.3/8.11.6) with ESMTP id g4F3E4ZX038498 for ; Tue, 14 May 2002 20:14:04 -0700 (PDT) (envelope-from lou@metron.com) X-Authentication-Warning: violet.metron.com: Host localhost.metron.com [127.0.0.1] claimed to be violet.metron.com Received: (from lou@localhost) by violet.metron.com (8.12.3/8.12.3/Submit) id g4F3E3mO038497 for freebsd-stable@FreeBSD.ORG; Tue, 14 May 2002 20:14:03 -0700 (PDT) (envelope-from lou@metron.com) X-Authentication-Warning: violet.metron.com: lou set sender to lou@metron.com using -f Date: Tue, 14 May 2002 20:14:03 -0700 From: Lou Katz To: freebsd-stable@FreeBSD.ORG Subject: Tar broken for large files? Message-ID: <20020514201403.A38469@metron.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a directory on a backup machine which contains gzipped epoch dumps of various file systems. I tried to tar the directory to a DDS3 tapedrive, and noticed that it finished awfully quickly. When I did a tar | dd of=tapedrive I saw that the number of bytes/blocks written was sorely lacking. uname -a: FreeBSD shadow.metron.com 4.5-RELEASE FreeBSD 4.5-RELEASE #0 The original directory: shadow# ls -l total 10278592 -rw-r--r-- 1 root wheel 26159161 May 10 03:03 epoch.root.gz -rw-r--r-- 1 root wheel 3668941475 Apr 28 21:06 epoch.users.gz -rw-r--r-- 1 root wheel 33832960 May 10 03:14 epoch.usr.gz -rw-r--r-- 1 root wheel 150377578 May 13 04:48 epoch.work.gz -rw-r--r-- 1 root wheel 4445344874 May 13 04:48 epoch.work.gz.orig -rw-r--r-- 1 root wheel 2197885923 May 5 17:41 local.tgz tarring to a tapedrive, then reading the tape: shadow# tar -cvf /dev/rsa0 * epoch.root.gz epoch.users.gz epoch.usr.gz epoch.work.gz local.tgz shadow# tar -tvf /dev/rsa0 -rw-r--r-- root/wheel 26159161 May 10 03:03 2002 epoch.root.gz -rw-r--r-- root/wheel -626025821 Apr 28 21:06 2002 epoch.users.gz -rw-r--r-- root/wheel 33832960 May 10 03:14 2002 epoch.usr.gz -rw-r--r-- root/wheel 150377578 May 13 04:48 2002 epoch.work.gz -rw-r--r-- root/wheel -2097081373 May 5 17:41 2002 local.tgz Extracting, for instance epoch.work.gz, which appears to be woefully small, results in shadow# gunzip < epoch.work.gz|restore -tvf - Verify tape and initialize maps Dump date: Mon May 13 03:01:00 2002 Dumped from: the epoch Level 0 dump of /work on violet.metron.com:/dev/ar0s1e Label: none Extract directories from tape Mangled directory: reclen not multiple of 4 ^Crestore interrupted, continue? [yn] n Here is the attempt to see what is going on: shadow# tar -cf - * | dd bs=40k of=/dev/rsa0 0+20545 records in 0+20545 records out 210380800 bytes transferred in 295.953683 secs (710857 bytes/sec) Obviousls, tar is not copying things correctly. Is this a known bug? # tar --version GNU tar version 1.11.2 -- -=[L]=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message