search for: report_write_error

...diff_ignore rsync-3.0.5_base/receiver.c rsync-3.0.5/receiver.c --- rsync-3.0.5_base/receiver.c 2008-11-15 16:49:28.000000000 -0600 +++ rsync-3.0.5/receiver.c 2009-03-10 22:18:20.000000000 -0500 @@ -297,6 +315,16 @@ if (fd != -1 && offset > 0 && sparse_end(fd) != 0) { report_write_error: + fprintf(stderr, "rsync: write failed on %s: %s\n", full_fname(fname), strerror(errno)); rsyserr(FERROR_XFER, errno, "write failed on %s", full_fname(fname)); exit_cleanup(RERR_FILEIO);

...c,v retrieving revision 1.110 diff -u -p -r1.110 receiver.c --- receiver.c 27 Nov 2004 17:56:58 -0000 1.110 +++ receiver.c 2 Dec 2004 16:40:23 -0000 @@ -289,7 +289,8 @@ static int receive_data(int f_in, char * offset += len; } - flush_write_file(fd); + if (flush_write_file(fd) < 0) + goto report_write_error; #ifdef HAVE_FTRUNCATE if (inplace && fd != -1) The above patch is relative to the latest CVS sources on the trunk. With the above knee-jerk patch, I do get the write error I want, but also some other probably undesirable diagnostics: $ ./rsync in /full/tmp rsync: write failed on...

...c,v retrieving revision 1.110 diff -u -p -r1.110 receiver.c --- receiver.c 27 Nov 2004 17:56:58 -0000 1.110 +++ receiver.c 2 Dec 2004 16:40:23 -0000 @@ -289,7 +289,8 @@ static int receive_data(int f_in, char * offset += len; } - flush_write_file(fd); + if (flush_write_file(fd) < 0) + goto report_write_error; #ifdef HAVE_FTRUNCATE if (inplace && fd != -1) The above patch is relative to the latest CVS sources on the trunk. With the above knee-jerk patch, I do get the write error I want, but also some other probably undesirable diagnostics: $ ./rsync in /full/tmp rsync: write failed on...

...2008-12-04 17:01:00.000000000 -0500 @@ -38,6 +38,7 @@ extern int preserve_hard_links; extern int preserve_perms; extern int preserve_xattrs; +extern int copy_devices; extern int basis_dir_cnt; extern int make_backups; extern int cleanup_got_literal; @@ -285,7 +286,7 @@ goto report_write_error; #ifdef HAVE_FTRUNCATE - if (inplace && fd != -1 + if (inplace && !copy_devices && fd != -1 && ftruncate(fd, offset) < 0) { rsyserr(FERROR_XFER, errno, "ftruncate failed on %s", full_fname(fn...

...ame_r, int fd_r, OFF_T size_r, const char *fname, int fd, OFF_T total_size) { + STRUCT_STAT st; static char file_sum1[MAX_DIGEST_LEN]; static char file_sum2[MAX_DIGEST_LEN]; struct map_struct *mapbuf; @@ -285,10 +287,14 @@ goto report_write_error; #ifdef HAVE_FTRUNCATE - if (inplace && fd != -1 - && ftruncate(fd, offset) < 0) { - rsyserr(FERROR_XFER, errno, "ftruncate failed on %s", - full_fname(fname)); + (void)do_fstat(fd,&st); + /* Makes no...

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 : >

...read_size, sum.blength); @@ -231,11 +245,18 @@ stats.literal_data += i; cleanup_got_literal = 1; - sum_update(data, i); + if (f_in >= 0) + /* no need for md4 during fast copy -goldor */ + sum_update(data, i); if (fd != -1 && write_file(fd,data,i) != i) goto report_write_error; offset += i; + if (f_in < 0 && percent < offset * 100 / total_size) { + /* report progress of fast copy to sender every 1% -goldor */ + write_buf(local_socket, (char *)&offset, sizeof(offset)); + percent = offset * 100 / total_size; + } continue; } @@ -3...

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.