Big Copies keep failing

[LuKreme]

On 3-Aug-2007, at 22:22, Hex Star wrote:
> cp -Rfv /Volumes/srcvolumename /Volumes/destvolumename

wtf?  -f? why would you use -f? besides, if you are going to use cp  
for something like this you really probably want to use -p to  
preserve as much metadata as possible. Also, the cp command in Tiger  
copies resource forks without a problem.  If I could find a resource  
fork file I'd test to be sure, but I can't find one.  Oh, wait, text  
clippings use resource forks, right?

  $ ls -ls wtf\?\ \ -f\?\ why\ would\ you\ use\ .textClipping
16 -rw-r--r--   1 kreme  kreme  0 Aug  4 07:07 wtf?  -f? why would  
you use .textClipping
  $ cp wtf\?\ \ -f\?\ why\ would\ you\ use\ .textClipping test.clipping
  $ ls -ls test.clipping
16 -rw-r--r--   1 kreme  kreme  0 Aug  4 07:08 test.clipping
  $ ls -ls test.clipping/rsrc
16 -rw-r--r--   1 kreme  kreme  4779 Aug  4 07:08 test.clipping/rsrc
   $ ls -ls wtf\?\ \ -f\?\ why\ would\ you\ use\ .textClipping/rsrc
16 -rw-r--r--   1 kreme  kreme  4779 Aug  4 07:07 wtf?  -f? why would  
you use .textClipping/rsrc
   $ diff wtf\?\ \ -f\?\ why\ would\ you\ use\ .textClipping  
test.clipping
   $ diff wtf\?\ \ -f\?\ why\ would\ you\ use\ .textClipping/rsrc  
test.clipping/rsrc
   $

Still, I would do the following instead:

rsync -av <source> <destination> > ~/rsync.log &

then I would look at rsync.log when the 'copy' is done for any failures.

-- 
It's Tchaikovsky's 'Another One Bites the Dust'," said Crowley,  
closing his eyes as they went through Slough.