RSYNC is your friend.
rsync -a -S sourcedir/. targetdir/.
where "-S" means "handle sparse files intelligently". TAR also has an
option for handling sparse files.
-- R; <><
On Wed, Jul 21, 2010 at 11:59, Berry van Sleeuwen
<berry.vansleeu...@xs4all.nl> wrote:
> Hello Edmund,
>
> Sparse files. OK. Then the next question, how can I store a 26G file in
> a machine that isn't that large? And to add to this, why does the
> filesystem backup really dump 26G into our TSM server?
>
> So it looks like the data is going somewhere.
>
> Berry.
>
> Op 21-07-10 15:41, Edmund R. MacKenty schreef:
>>
>> Because they are sparse files. Linux only allocates blocks for a file that
>> have actually been written, so if a process creates a file and seeks a couple
>> of gigabytes into it before the first write, the file size is reported as
>> over 2GB, but it really only uses the blocks actually written after that
>> point. Use du(1) to report the actual space used by those files.
>>
>>
>>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
