[Netkit.users] parse support in archive ?

[Massimo Rimondini]

Hi Julien,

you did mean "sparse"... ;-)

As sparse files are a filesystem feature, copying over the network cannot
but transfer the whole file, unless compression has been applied beforehand.
If you are using tar for compression, there is a -S (or --sparse) that
enables handling of sparse files. It should be used only when creating the
compressed archive (see
http://www.gnu.org/software/tar/manual/html_node/sparse.html#SEC133).

Also, I suggest checking that the destination filesystem has support for
sparse files (ext, NTFS, Reiser, XFS do, just to mention a few; a more
complete list can be found at
http://en.wikipedia.org/wiki/Comparison_of_file_systems#Allocation_and_layou
t_policies).

Cheers,
Massimo.


> -----Original Message-----
> From: netkit.users-bounces a list.dia.uniroma3.it [mailto:netkit.users-
> bounces a list.dia.uniroma3.it] On Behalf Of Julien Iguchi-Cartigny
> Sent: Saturday, April 24, 2010 1:17 PM
> To: Users of the Netkit Network Emulation System
> Subject: [Netkit.users] parse support in archive ?
> 
> Hi,
> 
> I've a small problem. i've modify the main fs and i want to use it on an
> other computer. But whatever i did (copy by ssh, archive ith with
tar.bz2),
> the fs is fully create (without parse attribute, so it took 10Go). Does
> anyone know how to keep the parse attribute of a fs ?
> 
> Cheers,
> 
> julien.