From owner-freebsd-questions@FreeBSD.ORG Tue Aug 11 03:08:38 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF6F61065678 for ; Tue, 11 Aug 2009 03:08:38 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8F3EB8FC20 for ; Tue, 11 Aug 2009 03:08:38 +0000 (UTC) Received: from smoochies.rachie.is-a-geek.net (mailhub.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 5C9047E821; Mon, 10 Aug 2009 19:08:37 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Mon, 10 Aug 2009 19:08:35 -0800 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA2; KDE/4.2.4; i386; ; ) References: <6206A242-7226-48E3-8D09-A1D3A651F2A8@socket.net> <20090810170921.GC49364@slackbox.xs4all.nl> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908101908.36042.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: Roland Smith , Jay Hall Subject: Re: Backup Size X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 03:08:39 -0000 On Monday 10 August 2009 18:24:19 Jay Hall wrote: > On Aug 10, 2009, at 12:09 PM, Roland Smith wrote: > >> The fact that you are using tar also plays a part. Tar has some > >> overhead to > >> store information about the files it contains. > > Is it possible to calculate the amount of overhead tar will use? Difficult. 512 bytes per entry + 1024 (EOF). See man 5 tar. But since files will be padded there is some extra overhead. Also, it is hard to calculate hard links and sparse files. Tar will handle these correctly (i.e. preserve hard links and detect sparse files and try not archive "blocks of nulls") but it is hard to calculate the size because of this before the archive operation because of this. -- Mel