system response issue

[g]

double oops.

my thinking and typing were out of sync.

On 07/13/15 23:16, g wrote:
> On 07/13/15 21:54, jd1008 wrote:
>> On 07/13/2015 08:43 PM, g wrote:
> <<<>>>
> 
>>> 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.
> 
> oops. -x = extract.
> 
>>> just what is your actual command line?
>>>
>>>
>> tar cf - BigDirArchive | tar -C  /sdc1 -xpvf -
>>

should have read:

> ok. that does make for better understanding.

as a suggestion;

> i stopped using tar years ago in favor of cpio, which has more advantages,
> when i was using tape for archiving. works well with usb memory and usb
> hdd drives. in fact, when i archive paths between hdd partitions or drives,
> i use cpio instead of "cp -R".
> 
> to perform same using cpio, command line would be;
> 
>   find path2BigDirArchive -depth -print0 | sort | cpio -p -adm  /sdc1
> or
>   find . -depth -print0 | sort | cpio -p -adm  /sdc1
> 
> in above, "-p" is 'copy-pass mode', equivalent to "|" and "-x" in tar.
> 
> because you are having response time issues with usb, i believe you will
> find cpio to be more favorable than using tar.


-- 

peace out.

-+-
If Bill Gates got a dime for every time Windows crashes...
 ...oh, wait. He does. THAT explains it!
-+-
in a world with out fences, who needs gates.
-+-

CentOS GNU/Linux 6.6

tc,hago.

g
.