On Mon, Aug 10, 2009 at 09:24:19PM -0500, 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
On Aug 11, 2009, at 12:09 PM, Roland Smith wrote:
Just execute the tar command, and dump the output to /dev/null
through dd:
tar -cf - /etc |dd of=/dev/null
tar: Removing leading '/' from member names
3160+0 records in
3160+0 records out
1617920 bytes transferred in 0.057690 secs (28045115
On Mon, Aug 10, 2009 at 10:21:58AM -0500, Jay Hall wrote:
I am sure there is an easy explanation for this, but I cannot find it.
I am backing up my /etc directory using the following command.
tar -cvf - /etc | dd of=/dev/nsa1 obs=10240
Why are you using dd? Tar was originally built to
In the last episode (Aug 10), Jay Hall said:
I am sure there is an easy explanation for this, but I cannot find it.
I am backing up my /etc directory using the following command.
tar -cvf - /etc | dd of=/dev/nsa1 obs=10240
When the command completes, I receive the following message.
On Mon, Aug 10, 2009 at 06:25:28PM +0200, Roland Smith wrote:
On Mon, Aug 10, 2009 at 10:21:58AM -0500, Jay Hall wrote:
I am sure there is an easy explanation for this, but I cannot find it.
I am backing up my /etc directory using the following command.
tar -cvf - /etc | dd
On Mon, 10 Aug 2009 10:21:58 -0500, Jay Hall jh...@socket.net wrote:
What concerns me is when running du -h /etc, the size of the folder is
reported as 1.7M.
Excuse me for being pedantic, but please try to use the correct
terminology. There are no folders in FreeBSD. The concept you
are
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?
Thanks,
Jay
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
