On 07/13/2015 08:43 PM, g wrote:
On 07/13/15 21:17, jd1008 wrote:
On 07/13/2015 06:52 PM, g wrote:
more for thought, is tar building finale file in memory, /tmp, or on the usb3 drive?
:) Well, since I was using a pipe, I assume swap backed memory is used. However, the un-tar process is running in parallel, so the RAM pipe is shared between the producer "tar" and the consumer tar, which populates the destination directory with the contents of the source directory. That said, I do not think that the entirety of the source dir is first copied to the "pipe", before it is then consumed by the "un"tar process. I think the RAM pipe is being read (emptied), as the producer fills it (using thread synchronization primitives). Just my guess. I have not looked at tar's source code.
ok. you have now thrown in *pipe* and process *un-tar*.
are you using tar to pass files to target and have them end up as separate files, or as a single archive file?
ria, all i see in your original post is "tar -C /sdc1 -xpvf" which would indicate archiving to a single file.
just what is your actual command line?
tar cf - BigDirArchive | tar -C /sdc1 -xpvf -