search for: finish_hard_link

https://bugzilla.samba.org/show_bug.cgi?id=5407 Summary: hlink.c:480: finish_hard_link: Assertion `flist != ((void *)0)' failed. Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba....

...is reached and then hardlinking from that point forward -- if that's what the git head code really does.) Glancing over the code, it seems to me the way to do this is to have the hard_link_one() return value indicate when failure is EMLINK. This can then be tested for during the execution of finish_hard_link(). When link exhaustion is detected in finish_hard_link(), && link_dest, then report an error but also copy the source file and re-run finish_hard_link() to undo/fix-up the hard links already created. This assumes that the hard links created so far can be overwritten and won't break t...

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 QAContact...

...doesn't demonstrate the effect) $ cd .. $ rsync -aHv --link-dest ../b/ a/ c/ ... a18185 => a100 a18186 => a100 rsync: link "/tmp/c/a18187" => a100 failed: Too many links (31) rsync: link "/tmp/c/a182" => ../b/a182 failed: Too many links (31) rsync: hlink.c:449: finish_hard_link: Assertion `flist != ((void *)0)' failed. rsync: connection unexpectedly closed (65601 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(598) [sender=3.0.0cvs] Repeating the rsync command while the 'c' directory is left intact after the...

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: connection unexpectedly closed (54286 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] args used (approx, as they were pass...

...lags, 0, NULL); } - if (code != FNONE && verbose) + if ((iflags & ITEM_REPORT_CHANGE) && code != FNONE && verbose) rprintf(code, "%s -> %s\n", fname, sl); #ifdef SUPPORT_HARD_LINKS if (preserve_hard_links && F_IS_HLINKED(file)) finish_hard_link(file, fname, ndx, NULL, itemizing, code, -1); #endif - /* This does not check remove_source_files == 1 - * because this is one of the items that the old - * --remove-sent-files option would remove. */ - if (remove_source_files) + /* When the symlink value changed, we do not check +...

...in/rsync --verbose -e ssh -l -rltzuHAX --delete --force --exclude="*~" --exclude=feed --exclude="upload" --exclude=spam_statistics.html ~sb/public_html/penguin/public_html/ utx at penguin.cz:public_html/ I experienced following abort message during syncing: rsync: hlink.c:536: finish_hard_link: Assertion `node != ((void *)0) && node->data != ((void *)0)' failed. rsync: [sender] write error: Broken pipe (32) rsync error: unexplained error (code 255) at io.c(829) [sender=3.1.1] Local side is openSUSE 13.2 x86_64: sync version 3.1.1 protocol version 31 Copyright (C) 1996-...

...ard linked backups) easily exceeds the hard link limit of ext4. This causes an error message like the following: rsync: link "/var/lib/iserv/backup/mnt/mapper-martin-ext4/lvmtest/partial/hardlinks/14497" => hardlinks/1 failed: Too many links (31) File-list index 0 not in 5087 - 35088 (finish_hard_link) [generator] rsync error: protocol incompatibility (code 2) at rsync.c(652) [generator=3.0.9] rsync error: received SIGUSR1 (code 19) at main.c(1316) [receiver=3.0.9] It would be nice to have an additional option like --break-hard-links that works like this: 1) if the --link-dest dir contains an...

...compress-level=9 --stats Server1-*-2009-10-* REMOTE:/backup/ After a wile it gives me this and aborts: rsync: stat "/path/directory/!path with spaces/FILE.EXT" failed: No such file or directory (2) message repeated 20 to 50 times Assertion failed: (CVAL(node->data, 0) == 0), function finish_hard_link, file hlink.c, line 533. rsync: stat "/path/directory/!path with spaces/FILE.EXT" failed: No such file or directory (2) message repeated about 5 times. rsync error: unexplained error (code 134) at io.c(1143) [sender=3.0.6] # rsync --version rsync version 3.0.6 protocol version 30 Copyr...

...} + if (verbose) + rprintf(code, "%s -> %s\n", fname, sl); +#ifdef SUPPORT_HARD_LINKS + if (preserve_hard_links && F_IS_HLINKED(file)) + finish_hard_link(file, fname, ndx, NULL, itemizing, code, -1); +#endif + if (remove_source_files) + goto return_with_success; + goto cleanup; } - /* Not the right symlink (...

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

Rsync version 3.0.5pre2 is now available for release testing. This is a bug-fix release. I hope this is the final pre-release for 3.0.5, so please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. The changes since 3.0.5pre1: - Fixed the use of a dot-dir path (e.g. foo/./bar) inside a --files-from file when the root of the transfer

Rsync version 3.0.5pre2 is now available for release testing. This is a bug-fix release. I hope this is the final pre-release for 3.0.5, so please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. The changes since 3.0.5pre1: - Fixed the use of a dot-dir path (e.g. foo/./bar) inside a --files-from file when the root of the transfer