search for: big_fil

...ssuming if I don't have partial flag any partially transferred files should be deleted. However this is not what I'm seeing. Example: (Using a big file so that rsync times a while to run. This gives me time to hit CTRL-C for the SIGINT). > mkdir example > dd if=/dev/zero of=example/big_file bs=1024 count=102400 > ls -l example -rw-r--r-- 1 jmitchell users 104857600 2006-05-18 16:33 big_file > rsync -ptgou example/big_file . # Let it run for a couple of seconds to start running, then hit CTRL-C rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(242) [sender...

...source file is overwritten whilst an rsync is in progress. Instead of the destination file being truncated, or an error being raised and the destination file removed, I get a file of the correct length, but mostly full of nulls where previously there were none. An example is shown here: > ls -l big_file -rw------- 1 jonm users 168797799 Jan 30 09:06 big_file > ls -l small_file -rw-r--r-- 1 jonm users 9212 Jan 30 09:09 small_file > od -c -j 168797700 big_file # show the tail of the big file 1203723004 e R a t e T r u n c \0 \0 \0 \0 \0 \0 1203723024 001 017...

Typically rsync exits and reports an error such as: rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: write failed on "/Volumes/Backup/big_file.dmg": No space left on device (28) rsync: connection unexpectedly closed (67174 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /src/ rsync-3.0.5/io.c(600) [sender=3.0.5] when it runs out of space on the destination. On a few occasions, h...

I am involved with the development of lbackup. This message to the rsync mailing list is related to the following thread on the lbackup-disccussion mailing list : http://tinyurl.com/lbackup-discussion-diskfull Essentially, I am curious to if any one using rsync 3.0.7 on Mac OS (10.6) Server has experienced an out of disk space error and not had a message similar to the following reported : >

...ls. We used the --max-size parameter to skip these files: however, we did not like the lack of warning about skipped files. This patch adds another parameter, --warn, to select the output of a warning message when files bigger than the selected --max-size are skipped. The message is of the form: big_file is over max-size 3. For information: our backups are controlled from the destination of the backups (pull rather than push as Kevin Korb recently advised). We use the rsync daemon capability. The destinations of our backups are file systems subject to HSM (Hierarchical Storage Management), usin...

Hello every body. Well, my question is very simple . I Have a HVM working fine ( I hope so ... ) on a CentOS 5.1 , xen 3.1. I created config file by hand .. I''m not using virtmanager from CentOS .. I '' m using LVM dev w/o file system formated. My HDA is configured like this: disk = [ ''phy:/dev/vms_1/win01,hda,w'' ] My question , what is the diference if I