Re: Transfering very large files / and restarting failures

2005-07-28 Thread Wayne Davison
On Wed, Jul 27, 2005 at 04:29:46PM -0700, Todd Papaioannou wrote: Not sure I have the mojo to mess with the patches though! I applied the --append patch to the CVS source, so if you want to snag version 2.6.7cvs, you can grab it via the latest nightly tar file:

Transfering very large files / and restarting failures

2005-07-27 Thread Todd Papaioannou
Hi, My situation is that I would like to use rsync to copy very large files within my network/systems. Specifically, these files are in the order of 10-100GB. Needless to say, I would like to be able to restart a transfer if it only partially succeeded, but NOT repeat the work already done.

Transfering very large files / and restarting failures (again)

2005-07-27 Thread Todd Papaioannou
Woops! In my last email, I meant to say the second command was: rsync --no-whole-file --progress theFile /path/to/dest Todd Hi, My situation is that I would like to use rsync to copy very large files within my network/systems. Specifically, these files are in the order of 10-100GB. Needless

Re: Transfering very large files / and restarting failures

2005-07-27 Thread Wayne Davison
On Wed, Jul 27, 2005 at 01:50:39PM -0700, Todd Papaioannou wrote: where both theFile and /path/to/dest are local drives. [...] rsync -u --no-whole-file --progress theFile /path/to/dest When using local drives, the rsync protocol (--no-whole-file) slows things down, so you don't want to use it

RE: Transfering very large files / and restarting failures

2005-07-27 Thread Todd Papaioannou
Wayne, Thanks for the swift answers and insight. However, the stats shown during the progress seem to imply that the whole transfer is starting again. Yes, that's what rsync does. It retransfers the whole file, but it uses the local data to make the amount of data flowing over the