From owner-freebsd-current@FreeBSD.ORG Mon Sep 26 19:58:12 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07F8616A41F for ; Mon, 26 Sep 2005 19:58:12 +0000 (GMT) (envelope-from emaste@phaedrus.sandvine.ca) Received: from mailserver.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DE3E43D49 for ; Mon, 26 Sep 2005 19:58:08 +0000 (GMT) (envelope-from emaste@phaedrus.sandvine.ca) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by mailserver.sandvine.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 26 Sep 2005 15:58:04 -0400 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 406891364A; Mon, 26 Sep 2005 15:58:07 -0400 (EDT) Date: Mon, 26 Sep 2005 15:58:07 -0400 From: Ed Maste To: freebsd-current@freebsd.org Message-ID: <20050926195807.GD95971@sandvine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 26 Sep 2005 19:58:04.0789 (UTC) FILETIME=[9B83D250:01C5C2D4] Subject: Bsdtar and archive torture tests X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2005 19:58:12 -0000 In 16.11 "Backup Basics" the handbook mentions a paper by Elizabeth D. Zwicky and presented at LISA V in 1991. She tested a number of archive and backup programs, including GNU tar and other tar implementations, and dump/restore. I've found that she's presented an updated version of the paper at LISA XVII in 2003[1]. I ran the set of testcases she developed against gtar and bsdtar, after deleting the "holes" subdirectory. (The test included a sparse file with a 0.5TB hole. Without support for sparse files, bsdtar quickly filled my disk so I didn't bother with those tests.) To run the test, I did cd /d2/archive_test/original tar -cf /d2/archive_test/bsdtar.tar . cd /d2/archive_test/bsdtar_recovered tar -xpf /d2/archive_test/bsdtar.tar perl dircmp.pl original bsdtar_recovered | less The dircmp.pl script produced more than 60000 lines of the form Symlink target changed from ../longfilenames/84 to ../longfilenames/84 as well as some other issues. It appears that all of the "symlink target changed" cases have both a long name and some high-bit characters. I haven't had any time to look into what might cause this, but just wanted to mention the availability of these testcases and some initial results. For reference, gtar runs into a few issues with long names, but doesn't change symlink targets. [1] http://www.usenix.org/events/lisa03/tech/full_papers/zwicky/zwicky_html/index.html -- Ed Maste, Sandvine Incorporated