[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Understanding sparse-files


  • To: "John Haxby" <john.haxby@xxxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Tue, 16 Dec 2008 16:13:49 -0500
  • Cc: "Rustedt, Florian" <Florian.Rustedt@xxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 16 Dec 2008 13:15:13 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=ec6w+EE0h6moIGntFt6F2Edp9EYJ6kZJIvqb4FwKroatmm9a5yeuaYjydZmVfge5zY WUTGFFGUsKBbW8kukmDdJnSDujDm4vB114AjyivriyjMoJYr44QL3974/ne9Iua+FP/+ 7Q7ukprr5jo8qPCO4/OpDMy/yhr7wYiOPZ8O4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> There are some problems with sparse files: the compress beautfully (gzip
> reports 99.9%) but it takes a while to read the empty space and when you
> uncompress the file you discover that it now actually occupies disk space:
> there's no good way to distinguish between an unallocated block and a block
> full of zeroes.   This also means that you need to be careful how you back
> these files up: you need something a little cleverer than gzip.

You can use tar with the S (sparse) option here.
Also I think that you should be able to use cp
with a --sparse option as well.

To distinguish, using the du command helps.

Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.