search for: send_file_nam

...ching to program: /home/doli/progz/rsync-2.6.1pre-1/rsync, process 30131 0x2a344742 in ?? () (gdb) bt #0 0x2a344742 in ?? () #1 0x2a3a2d20 in ?? () #2 0x00000020 in ?? () #3 0x598062b0 in ?? () #4 0x0805a150 in make_file (fname=0x0, flist=0x0, exclude_level=69) at flist.c:879 #5 0x0805a3bc in send_file_name (f=3, flist=0x41, fname=0x0, recursive=65, base_flags=0) at flist.c:932 #6 0x0805a845 in send_file_list (f=1, argc=1501590384, argv=0x0) at flist.c:1033 #7 0x08053e1a in hash_search (f=1, s=0x0, buf=0x0, len=577936410078638920) at match.c:170 #8 0x08054003 in hash_search (f=1, s=0x0, buf=0x0, l...

https://bugzilla.samba.org/show_bug.cgi?id=1448 Summary: core dump in send_file_name Product: rsync Version: 2.6.2 Platform: x86 OS/Version: NetBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: eravin@panix.com QAContact: rs...

https://bugzilla.samba.org/show_bug.cgi?id=1448 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From wayned@samba.org 2004-06-09 13:54

...can't figure out why exactly it crashes. I hope that someone on this list can give me a hint on that. This is the debug output (appeared when I tried to copy a local directory to another location): FDBX0302: calling f_name(f = 0x1EA94000, fbuf = ".s.-.~~q.s.-.~~..~~.") from function send_file_name FDBX0303: returning <no value> from f_name FDBX0302: calling f_name(f = 0x1EA93FC8, fbuf = "") from function send_file_name FDBX0303: returning <no value> from f_name FDBX0302: calling f_name(f = 0x1EA93F90, fbuf = "open") from function send_file_name FDBX0303: retu...

rsync-2.6.6 manpage says: --delete [...] This option has no effect unless directory recursion is enabled. True. In fact, I noted that --delete doesn't delete anything if --dirs is used rather than --recursive. Is there any reason for --delete not to delete when used with --dirs? Is there a way to get rsync to actually delete files on the receiving end when using

...ly lost in loss record 27 of 30 at 0x4A05E46: malloc (vg_replace_malloc.c:195) by 0x41DFD7: _realloc_array (util.c:1438) by 0x41EC36: expand_item_list (util.c:1690) by 0x43C3DE: rsync_xal_get (xattrs.c:268) by 0x43C602: get_xattr (xattrs.c:309) by 0x4076EF: send_file_name (flist.c:1433) by 0x40817D: send_directory (flist.c:1673) by 0x408991: send1extra (flist.c:1827) by 0x408D23: send_extra_file_list (flist.c:1899) by 0x417345: send_files (sender.c:184) by 0x42110A: client_run (main.c:1039) by 0x421B9B: start_client (main.c...

...)) { + for (errno = 0, di = readdir(d); di; errno = 0, di = readdir(d)) { char *dname = d_name(di); if (dname[0] == '.' && (dname[1] == '\0' || (dname[1] == '.' && dname[2] == '\0'))) continue; strlcpy(p, dname, MAXPATHLEN - l); send_file_name(f, flist, fname, recurse, 0); + } + if ( errno ) { + io_error = 1; + rprintf(FERROR, "readdir(%s): %s\n", dir, strerror(errno)); + /* Don't return yet; we want to clean up first */ } if (local_exclude_list) Index: rsync.c =====================================================...

...ot;... but EPIPE is never explicitly checked for in io.c, just assumed as the last case. Perhaps this should be handled more cleanly? There may be a timing issue here that could be handled with a sleep(). 2) The core file being thrown by my setup is for the parent rsync only - during flist.c: send_file_name, which would be for the writer task... but it's the reader task forked off that's apparently going into lala land and tanking the enterprise by triggering a SIGPIPE/EPIPE on write. So, advice to all seeing this error: have gdb handy to bind to the *second* rsync process, as it is the...

I have a script that does a weekly backup on a local backup harddrive with the following command: # rsync -aRxW --delete / /mnt/backup Today I got errors because the target drive was full. It appeared nothing on the targed drive ever got deleted. When I used the following command to backup only my home dir, it worked as it should. # rsync -aRxW --delete /home/joost /mnt/backup Using rsync

Wayne, I've been ruminating a bit on the qsorted flist and duplicate removal and have an idea. What if we removed end_file_entry() from send_file_name() and instead had a for(i=0; i < flist->count; ++i) send_file_entry(flist->files[i], f, ??) in send_file_list(). As near as i can tell this would be unnoticeable to the protocol. Once done the sort of the file list could be moved to precede sending it. Thus making the sort on the r...

...mand I'm running is: $ rsync -arHRv --numeric-ids --delete --exclude=/opt/dist/cdrom \ [paths] [server]:[path] If I whittle down what appears in [paths], then it works. $ gdb rsync rsync.core gdb> bt #0 0x280faf0d in strncmp () from /usr/lib/libc.so.4 #1 0x7 in ?? () #2 0x80597f7 in send_file_name (f=-1, flist=0x808a100, fname=0xbfbfe994 "etc/opt/TWWfsw", recursive=1, base_flags=1) at flist.c:929 #3 0x805a2fc in send_file_list (f=-1, argc=0, argv=0xbfbffa44) at flist.c:1178 #4 0x804c0ff in delete_files (flist=0x808a0c0) at receiver.c:102 #5 0x805177e in do_recv (f_in=0...

...-exclude-from /local/dba/scripts/shoprod1_exclude_applfiles.txt -rlvz -e ssh /prod/applmgr/1159/ applprod@twnprod2:/prod/applmgr/1159/ we get the followin error at different stages, e.g. build stage or after processing a few files: rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_name": broken Pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) we are using rsync2.6.2 protocol version 28. Im at a loss to understand why this is happening. I already tried -vv option -> same error comes after processing some files from the exclusion file If I u...

...51,5 @@ || (dname[1] == '.' && dname[2] == '\0'))) continue; + { unsigned name_len = strlcpy(p, dname, remainder); if (name_len >= remainder) { @@ -1671,4 +1672,5 @@ send_file_name(f, flist, fbuf, NULL, flags, filter_level); + } } -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

...org Created attachment 6298 --> https://bugzilla.samba.org/attachment.cgi?id=6298 Several changes to the fileflags.diff patch The attached patch improves the following: - The fileflags variable was occasionally referenced without being initialized - sx.st.st_flags is initialized in flist.c:send_file_name() so get_xattr has access to fileflags - rsync.c: Errors that occur in undo_make_mutable are now reported (I think this also resolves an issue in which rsync would report "Unknown error (0)") - rsync.c: make_mutable is now called in set_file_attrs allowing set_file_attrs to apply acls, x...

Destroy ACL-s on destination when no ACL-s differens between source and destination. Bug is somehow related with function send_file_name() called with negative file descriptor f. There is no such bug in 2.6.9 version, but there options "-X -A --deleted" can't be used (we have "Internal error: wrong write used in receiver."). If I fix this, avoid calling send_acl() & send_xattr() with negative descriptor...

...file_struct *make_file(char *fnam return NULL; } - if (one_file_system && st.st_dev != filesystem_dev) { - if (skip_filesystem(fname, &st)) - return NULL; - } - if (check_exclude_file(fname, S_ISDIR(st.st_mode) != 0, exclude_level)) return NULL; @@ -825,6 +794,8 @@ void send_file_name(int f, struct file_l } if (S_ISDIR(file->mode) && recursive) { + if (one_file_system && file->dev != filesystem_dev) + return; struct exclude_struct **last_exclude_list = local_exclude_list; send_directory(f, flist, f_name(file));

...void sum_update(char *p, int len); void sum_end(char *sum); ! void close_all(); void _exit_cleanup(int code, const char *file, int line); void cleanup_disable(void); void cleanup_set(char *fnametmp, char *fname, struct file_struct *file, *************** *** 84,89 **** --- 84,90 ---- void send_file_name(int f, struct file_list *flist, char *fname, int recursive, unsigned base_flags); struct file_list *send_file_list(int f, int argc, char *argv[]); + void send_batch_file_list( int f, struct file_list *flist ); struct file_list *recv_file_list(int f); int file_compare(struct file_stru...

...-exclude-from /local/dba/scripts/shoprod1_exclude_applfiles.txt -rlvz -e ssh /prod/applmgr/1159/ applprod@twnprod2:/prod/applmgr/1159/ we get the followin error at different stages, e.g. build stage or after processing a few files: rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_name": broken Pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) we are using rsync2.6.2 protocol version 28. Im at a loss to understand why this is happening. I already tried -vv option -> same error comes after processing some files from the exclusion file If I u...

...re"); - local_exclude_list = make_exclude_list(fname,NULL,0,0); + local_exclude_list = make_exclude_list(fname,local_exclude_list, + 0,0); } else { io_error = 1; rprintf(FINFO,"cannot cvs-exclude in long-named directory %s\n",fname); @@ -681,6 +698,7 @@ send_file_name(f,flist,fname,recurse,0); } + /* Free the exclude entries in local_exclude_list */ if (local_exclude_list) { add_exclude_list("!", &local_exclude_list, 0); } Binary files /home/sits/orig/rsync-2.4.6/flist.o and ./flist.o differ diff -r -u --exclude=.o --exclude=rsync --exc...

...2.6.0-dar/proto.h --- rsync-2.6.0/proto.h Sat Dec 6 16:07:27 2003 +++ rsync-2.6.0-dar/proto.h Mon Mar 8 13:37:07 2004 @@ -77,8 +77,28 @@ int link_stat(const char *path, STRUCT_STAT * buffer); struct file_struct *make_file(char *fname, struct string_area **ap, int exclude_level); +void send_file_name_ifhasrsrcfork(int f, struct file_list *flist, char *fname, + int recursive, unsigned base_flags); +void send_file_name(int f, struct file_list *flist, char *fname, + int recursive, unsigned base_flags); +struct file_list *send_file_list(int f, int argc, char *argv[]); +struct file_list *...