Is there any precedent for rsync creating 0 length files that should've had content in them? IE, has anyone ever seen this before? We were doing a roughly 1 terabyte transfer, and upon running a python script to verify the integrity of the transfer, we discovered a small number of files that were 0 length, that shouldn't have been, all in the same user's account. Thanks!
On Tue, Nov 30, 2004 at 12:10:05PM -0800, Dan Stromberg wrote:> Is there any precedent for rsync creating 0 length files that should've > had content in them?Are you using 2.6.3? Older rsync versions did not check the return of the close() call, which could result in lost information if a disk (or per-user quota) filled up. The latest rsync should not do that. ..wayne..