similar to: [Bug 8665] New: Crash in free_xattr(), from recv_generator()

https://bugzilla.samba.org/show_bug.cgi?id=8475 Summary: memory leak around free_xattr() and rsync_xal_free(), with -aX, 200 bytes per file and per directory Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=7489 Summary: rsyncd segfaults using daemon exclude filter Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: michael.roberts at hp.com

Dear rsync people, Today I tried to back up my computer using rsnapshot with the RPM version of rsync-acl 2.6.9pre1 that I built. I tried twice, and both times, rsync encountered some kind of assertion failure. I was trying to reproduce the crash with rsync-acl 2.6.9pre2 and noticed a different bug (described below); when I have a chance, I will go back and investigate the crash further. Rsync

The generator can skip a directory's contents altogether due to --ignore-non-existing, a daemon exclude, or a mkdir failure. On a --dry-run, the generator can also note the missingness of a directory while still scanning its contents. These two scenarios were conflated using a single set of missing_below/missing_dir variables in combination with transient increments in dry_run; this caused

The security.evm extended attribute is fully owned by the Linux kernel and cannot be directly written from userspace. Therefore, we can always skip it. --- xattrs.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/xattrs.c b/xattrs.c index b105392..3b72e61 100644 --- a/xattrs.c +++ b/xattrs.c @@ -255,6 +255,9 @@ static int rsync_xal_get(const char *fname,

On January 15, 2018 1:53 AM, Wayne Davison write: >I have made rsync 3.1.3pre1 available for testing. This release has a couple security fixes, a few new features, and a smattering of bug fixes. >Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. Incompatibility introduced at 3.1.3pre1. These are not present at master, which

https://bugzilla.samba.org/show_bug.cgi?id=13224 Bug ID: 13224 Summary: New file handling causes compile issues for NonStop port. Product: rsync Version: 3.1.3 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: core Assignee:

Sorry, my question was whether or not this issue has been resolved. Thanks Hello, I am having problems with rsync: recv_generator: mkdir "dirname" No such file or directory (2) stat dirname No such file or directory Which is the same problem reported in the link below: http://www.mail-archive.com/rsync@lists.samba.org/msg16446.html rsync

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in

Hi, I have a crash running rsync-3.0.6 and using the -X flag. The crash was in uncache_tmp_xattrs() when free was called on every xattr_item. However, the rsync_xal_l.items is a buffer, not a list, and so only the whole buffer should be freed, and not every item. Can anyone with git access please fix this? This is the patch: --- rsync-3.0.6/xattrs.c 2009-11-30 14:16:53.501050939 +0200

Hi, I'm using 2.6.9 but I get: recv_files phase=1 generate_files phase=2 recv_files phase=2 recv_files finished generate_files phase=3 deleting in home delete_in_dir(home) [generator] make_file(home/administ,*,2) Internal error: wrong write used in receiver. _exit_cleanup(code=2, file=io.c, line=1204): entered _exit_cleanup(code=19, file=main.c, line=1182): entered rsync error: received

I have made rsync 3.1.3pre1 available for testing. This release has a couple security fixes, a few new features, and a smattering of bug fixes. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a summary of the changes since 3.1.2, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.1.3pre1-NEWS You

I have made rsync 3.1.3pre1 available for testing. This release has a couple security fixes, a few new features, and a smattering of bug fixes. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a summary of the changes since 3.1.2, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.1.3pre1-NEWS You

Hi, this is the first time I've tryed to build a 64 Bit Version with acl's enabled - so I expect I could duplicate this with older versions too... Here's the build info: System: AIX 6100-07-01-1141 Compiler: IBM xlc CC=xlc_r -g CXX=xlC_r CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51 -D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O

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.

We've been running Samba on AIX 4.3.3 and we recently changed to a new server. Everything appeared to be running fine for a while, but then we decided to strip away the burst page from our prints by nulling out the burst page file.... and now the fun begins. Printing still works fine from a unix level, but attempting to print via samba appears to do absolutely nothing. The print commands in

I've added the options --min-age=SECONDS and --max-age=SECONDS to allow rsync to skip files based on how recently they were modified. Setting --min-age=30 (for example) would cause rsync to skip files that had been modified within the last 30 seconds. Setting --max-age=7776000 would cause rsync to skip files that had been modified more than 90 days ago (7776000 == 60*60*24*90). I realize

From: "Robin H. Johnson" <robbat2 at gentoo.org> Add new option --ignore-non-existing-directory, that is a variant of --ignore-non-existing, but applies ONLY to directories. This was previously proposed in bug #8366, but I indepentantly had a use case for it in the Gentoo infrastructure. X-URL: https://bugzilla.samba.org/show_bug.cgi?id=8366 X-URL:

https://bugzilla.samba.org/show_bug.cgi?id=10756 Summary: rsync can't create files or dirs in subdirs (sometimes?) Product: rsync Version: 3.1.1 Platform: All OS/Version: Linux Status: NEW Severity: regression Priority: P5 Component: core AssignedTo: wayned at samba.org

Hello, I've looked through all the postings and can't seem to find an answer to my delema. I have tested this on an XP and win2k box and get the same results. I'm trying to rsync a fairly large directory (approx. 1.6 GB) from a windows machine to a linux box for backup purposes. The process hangs at the same point everytime. When I try to rsync smaller portions of the same large