similar to: DO NOT REPLY [Bug 5407] New: hlink.c:480: finish_hard_link: Assertion `flist != ((void *)0)' failed.

https://bugzilla.samba.org/show_bug.cgi?id=7454 Summary: assertion failed in finish_hard_link() Product: rsync Version: 3.0.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: bas at debian.org

https://bugzilla.samba.org/show_bug.cgi?id=11161 Bug ID: 11161 Summary: rare crash in hlink.c:536 Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: sbrabec at

Hi, I'm having a problem using --link-dest and --hard-links when the fs hits the hard link limit (link(2) returns EMLINK). Using rsync 3.0.7 an error is thrown and the target file is not created. Glancing at git head it _looks_ like things could now be a little nicer. Perhaps the target file is copied instead of hard linked when hardlinking fails -- I've not tested it. Anyway, the

While using dirvish, I ran into a runaway rsync process, which was continually spewing errors after encountering a "Too many links" error. This was with 2.6.9. I tried it again with the latest cvs version, and now at least it doesn't endless-loop with errors, but instead gives an assertion error. To reproduce: $ cd /tmp $ mkdir a b $ cd a $ date > a $ x=1 $ while ln a a$x; do

Just a quick heads up to say I'm still getting this (reproducable) error while doing daily backups: rsync: generator.c:1872: check_for_finished_files: Assertion `flist != ((void *)0)' failed. rsync: writefd_unbuffered failed to write 4092 bytes [receiver]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1500) [receiver=3.0.0pre2] This is with cvs

BLS #rsync --version rsync version 3.0.4pre2 protocol version 30 Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes rsync comes with ABSOLUTELY NO

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the HLINK.C module. The cast on function argument for the qsort() routine was wrong, and not allowing the compile to complete. When the function definiton of the hlink_compare() is corrected to have the const qualifiers, the cast inside the qsort() function call is no longer

Familiar? protocol error on a local file copy? How can I have a proto incompat when it it is talking to itself?... This was on the ERROUT... rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) File-list index 531530 not in 531937 - 533437 (finish_hard_link) [generator] rsync error: protocol incompatibility (code 2) at rsync.c(652) [generator=3.0.9] rsync:

In debian bug #498083 (http://bugs.debian.org/498083) someone is getting segfaults reasonably consistently, however when using -vvvv it doesn't happen... Fortunately Sven was able to get a good backtrace. I can't quite see what's causing the problem; it does seem to be related to xattrs. Please see the bugs report at the url above for the details. Any help much appreciated. Paul

https://bugzilla.samba.org/show_bug.cgi?id=6821 Summary: Assertion failed so rsync crashes (path includes special char) Product: rsync Version: 3.0.6 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=6542 Summary: rsync: hlink.c:125: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed. Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=8053 Summary: Older C compilers don't allow in-line declarations flist.c:1653 Product: rsync Version: 3.0.8 Platform: All OS/Version: FreeBSD Status: NEW Severity: minor Priority: P5 Component: core AssignedTo: wayned at samba.org

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

Hello Everyone, I have been reading the rsync code for the past few days and Iam finding it hard to understand how the file list works. The info that I am looking for is - "Are the files processed in the same order in both the receiver and generator processes?". Thanx in advance for all the replies. zahed. -- View this message in context:

Hi, I've got another error that is not in the FAQ ;) Ran from a script in a directory that doesn't exist anymore: shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory building file list ... pop_dir /mnt/dar : No such file or directory rsync error: errors selecting input/output files, dirs (code 3) at flist.c(980) I guess

On behalf of the development team of R (www.R-project.org), I would like to report the following problem with recent versions of rsync. First, some background info. The R Development Core Team uses CVS for maintainins its source code archive. Additionally, there is a mechanism for "mirroring" some important (so-called recommended) extension packages from a CRAN (Comprehensive R

https://bugzilla.samba.org/show_bug.cgi?id=8411 Summary: invalid flist flag when using protocol 28 or 29 Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: unobe at cpan.org

Hi, I was wondering if anyone could give me advice regarding using the lmer command in lme4 package to do logistic regression (mixed effects model). I use the following command lmer(ISH ~ArrayPathology2, random=~1|PatientID, data=HSDB4.noNA, family="binomial") where ISH is outcome(0 or 1), ArrayPathology2 is the variable of interest(factor), PatientID is random effect(factor), and

Ok, I just setup the log file and this is what I see there: rsync on cdrive/Temp/pix.log from admx (141.214.137.139) transfer interrupted (code 3) at flist.c(812) I had to change [cdrive] from path = "c:\" to path = c: to get rid of '@ERROR: chdir failed' error. I am getting close but still need some help. Thanks in advance. Nishi > -----Original Message----- From:

So, like a lot of people, I am using --link-dest to do backups. My backup target is ext4 so with a hard link limit of 64K. I do end up with trying to create too many links at some point though and get the following sequence of events: rsync: link "/.snapshots/hourly.0/linux/usr/src/openwrt-r18617/build_dir/host/mpfr-2.4.1/tests/.deps/tui_sub.Po" =>