search for: ioerr_general

https://bugzilla.samba.org/show_bug.cgi?id=7809 Summary: I/O errors other than IOERR_GENERAL should not suppress deletion Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org Rep...

...- && S_ISLNK(st.st_mode)) { + if ((copy_links && x_lstat(thisname, &st, NULL) == 0 + && S_ISLNK(st.st_mode)) || x_stat(thisname, &st, NULL) != 0) { io_error |= IOERR_GENERAL; rprintf(FERROR, "symlink has no referent: %s\n", full_fname(thisname)); Summary: - should "vanished" message be report as INFO instead ERROR ? - can we detected --copy-unsafe-symlink for file outside chro...

Using rsync 2.6.0 with --verbose and doing a pull. >?receiving file list ... readlink "{FILENAME}" failed: >?No such file or directory >?done >?IO error encountered - skipping file deletion The file was a temporary file that was being deleted just as the rsync was run. So while the file list was being built, it was there when the directory was read but had vanished by the

...00000 +0200 @@ -1462,6 +1462,20 @@ if (dname[0] == '.' && (dname[1] == '\0' || (dname[1] == '.' && dname[2] == '\0'))) continue; + if (dname[0] == '\0') { + char replaced = 0; + io_error |= IOERR_GENERAL; + if (len > 0) { + replaced = fbuf[len+1]; + fbuf[len+1] = '\0'; + } + rprintf(FINFO, + "cannot send file with empty name %s\n", + full_fname(fbuf)); + if (replaced) + fbuf[len+...

I just received this bug report on Debian's rsync package. I've verified it. The entry from the manpage: -C [...] Finally, any file is ignored if it is in the same directory as a .cvsignore file and matches one of the patterns listed therein. Here the patterns of a .cvsignore file is apparently used to exclude file outside the directory where the .cvsignore file is found. Any

Hi, Wouldn't you know, I can't get rsync to throw an error during a copy. :) I need to put together some instructions for a guy that runs a WISP for him to look over before weekly backups are made (I'll be copying the files to /dev/null so any read errors can be caught). I can do the simple : rsync warning: some files vanished before they could be transferred (code 24) at

...strcpy(p, ".cvsignore"); - add_exclude_file(&exclude_list,fname,MISSING_OK,ADD_EXCL UDE); + add_exclude_file(&local_exclude_list,fname,MISSING_OK,AD D_EXCLUDE); // PS XXX } else { io_error |= IOERR_GENERAL; rprintf(FINFO, And in fact, reverting this change seems to "fix" the problem. (The code in 2.6.1 is slightly different, but to the same effect.) If rsync is called without the '-I' option, the problem does not seem to appear. Sorry for the rather lengt...

Hi! This problem gave me quite a headache tonight... I more or less have this source directory: hop@krautesel:/var/tmp$ ls -laR from/ from/: total 12 drwxrwxr-x 3 hop hop 4096 Feb 8 03:34 . drwxrwxrwt 6 root root 4096 Feb 8 03:34 .. drwxrwxr-x 2 hop hop 4096 Feb 8 03:18 CVS -rw-rw-r-- 1 hop hop 0 Feb 8

All, During development of a backup solution with rsync I experienced some failed backups because of RC 23, partial transfer. These were because the application using the data I was backing up, was still active, and had deleted a file inbetween rsync compiling the file list and then transfering the file. After some feedback from Wayne Davidson and JW Schultz suggesting the solution to this,

https://bugzilla.samba.org/show_bug.cgi?id=3653 Summary: Silence 'vanished files' messages Product: rsync Version: 2.6.8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: count-samba@flatline.de

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large