https://bugzilla.samba.org/show_bug.cgi?id=13522
--- Comment #3 from Wayne Davison ---
The download page mentions all of the ways to grab the source, including git:
https://rsync.samba.org/download.html
The git source is safe, as it only contains bug fixes since the last release.
--
You are r
https://bugzilla.samba.org/show_bug.cgi?id=13735
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=13692
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=12569
--- Comment #11 from Paul Slootman ---
Created attachment 14775
--> https://bugzilla.samba.org/attachment.cgi?id=14775&action=edit
proposed patch
This patch is based on the patch posted earlier, but checks the options
--delete-missing-args and -
https://bugzilla.samba.org/show_bug.cgi?id=13749
Bug ID: 13749
Summary: Add more extensions to DEFAULT_DONT_COMPRESS
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: enhancement
https://bugzilla.samba.org/show_bug.cgi?id=13735
--- Comment #3 from Sébastien Béhuret ---
Thank you for suggesting the patches repo. An improved checksum/maybe-checksum
algorithm would be great but there appears to be a lot of work to achieve this.
Checksums are very handy for special cases (e.g
https://bugzilla.samba.org/show_bug.cgi?id=5124
--- Comment #8 from Michael ---
+1 from me on this.
We have several situations where we need to copy a large number of very small
files, and I expect that having multiple file transfer threads, allowing say ~5
transfers concurrently, would speed up
https://bugzilla.samba.org/show_bug.cgi?id=5124
--- Comment #9 from Paul Slootman ---
The issue when copying a large number of small files is disk IO / seeking.
Check the wait for IO values using top / whatever when doing such a transfer.
Running multiple threads in such a situation will only cau
https://bugzilla.samba.org/show_bug.cgi?id=5124
--- Comment #10 from Scott Peterson ---
(In reply to Paul Slootman from comment #9)
Multiple connections also makes sense on high bandwidth links. I’ve never been
able to rsync at wire speed on a 40G link using only one connection.
--
You are rec
https://bugzilla.samba.org/show_bug.cgi?id=5124
--- Comment #11 from Scott Peterson ---
(In reply to Haravikk from comment #4)
SPDY has apparently evolved into QUIC. QUIC supports multiple streams, which
can be created by either end. There can be a huge number of these. It seems
like a sender of
https://bugzilla.samba.org/show_bug.cgi?id=13522
jief changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugzilla.samba.org/show_bug.cgi?id=11893
--- Comment #1 from BruXy ---
Hello,
I have fallen into the same trap described in this issue:
$ rsync -avvHPS --rsh='ssh' big_cache.tar.bz bruxy@remote:/mnt/data_cache/
opening connection using: ssh -l bruxy remote rsync --server
-vvlHogDt
https://bugzilla.samba.org/show_bug.cgi?id=11893
--- Comment #2 from BruXy ---
I am using:
rsync version 3.1.1 protocol version 31
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To uns
https://bugzilla.samba.org/show_bug.cgi?id=10748
--- Comment #1 from walter ---
5 years later, I detect the same problem - which is critical for me.
why has nothing happened on that bug?
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for m
https://bugzilla.samba.org/show_bug.cgi?id=10748
--- Comment #2 from Kevin Korb ---
--prune-empty-dirs only affects the file list that rsync is working from. That
means it handles dirs that are either really empty on the source or anything
that has been emptied via --exclude or --filter. Option
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #5 from Michal Ruprich ---
Created attachment 14872
--> https://bugzilla.samba.org/attachment.cgi?id=14872&action=edit
Patch for the rwrite function
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Pl
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #4 from Michal Ruprich ---
Hi,
we have encountered similar segfault a couple of years ago. As you can see here
in comment #2, the p *in shows that the input buffer's size and len are
unreasonably huge - len = 18446744073709532799, size
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #6 from Michal Ruprich ---
This has just freshly arrived yesterday. Same bug as before and as described
here.
https://bugzilla.redhat.com/show_bug.cgi?id=1683737
--
You are receiving this mail because:
You are the QA Contact for the
https://bugzilla.samba.org/show_bug.cgi?id=13820
Bug ID: 13820
Summary: rsync is not preserving ACLs
Product: rsync
Version: 3.1.3
Hardware: x64
OS: Linux
Status: NEW
Severity: major
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=13820
--- Comment #1 from Kevin Korb ---
You have -A backwards. If you want rsync to copy the ACLs you have to use -A.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omit
https://bugzilla.samba.org/show_bug.cgi?id=13820
--- Comment #2 from Paul Slootman ---
I think the point Dinesh is trying to make is that rsync is removing ACLs from
the destination even though it's not asked to preserve the source's ACLs (which
don't exist).
I think the problem is that rsync cr
https://bugzilla.samba.org/show_bug.cgi?id=13820
--- Comment #3 from Dinesh Reddy ---
(In reply to Paul Slootman from comment #2)
Thanks for the suggestion. --inplace is actually working for my case.
Our use-case is to distribute sparse file across the VMs (--sparse is being
used), hopefully, thi
https://bugzilla.samba.org/show_bug.cgi?id=13827
Bug ID: 13827
Summary: despite --copy-unsafe-links, rsync does not copy the
referent of symlinks that point one level outside the
copied tree
Product: rsync
Version
https://bugzilla.samba.org/show_bug.cgi?id=3314
Björn Jacke changed:
What|Removed |Added
Assignee|t...@samba.org |wa...@opencoder.net
Target Milestone|none
https://bugzilla.samba.org/show_bug.cgi?id=10494
--- Comment #2 from Adrian Torregrosa ---
We have found this same problem using rsync 3.1.2.
I have downloaded the source code for version 3.1.3, and found the following
lines in sender.c:
146 if (S_ISREG(file->mode) /* Symlinks & devices
https://bugzilla.samba.org/show_bug.cgi?id=10494
--- Comment #3 from Adrian Torregrosa ---
Another option that I tried and verified, and that could make more sense, would
be to replace
141 if (do_lstat(fname, &st) < 0) {
with
141 if (do_stat(fname, &st) < 0) {
--
You are rece
https://bugzilla.samba.org/show_bug.cgi?id=10494
--- Comment #4 from Wayne Davison ---
In my prior testing I apparently missed that the symlink verification issue was
caused by -L (--copy-links). I have amended the change to use do_stat() when
--copy-links is enabled.
--
You are receiving this
https://bugzilla.samba.org/show_bug.cgi?id=13827
Wayne Davison changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=13522
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=11338
Wayne Davison changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugzilla.samba.org/show_bug.cgi?id=13820
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=13827
--- Comment #2 from Jan Bredereke ---
(In reply to Wayne Davison from comment #1)
Thanks, I see your point now.
Thus the problem is that the subject is rather complex, and the
man-page is quite terse on these details. A user can make a mistake
ea
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #8 from Michal Ruprich ---
Great, thanks Wayne.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change option
https://bugzilla.samba.org/show_bug.cgi?id=10494
--- Comment #5 from Adrian Torregrosa ---
I embedded the modified sender.c into 3.1.3's original source code, compiled
and tested, and I found it to have solved the problem: first I tried uploading
a softlink and deleting, then I tried uploading a
https://bugzilla.samba.org/show_bug.cgi?id=13609
--- Comment #3 from roland ---
what is the source and what is the remote filesystem ?
what does iostat tell on the source and the destination?
what's the size of the sparse files and how much of data is "inside" ?
--
You are receiving this mai
https://bugzilla.samba.org/show_bug.cgi?id=13609
--- Comment #4 from Dave Gordon ---
How about using truss/strace/whatever the OSX equivalent is to get a count of
all system calls made, when run with and without the --sparse option. Total
time on each type of call would be useful too.
If you fin
https://bugzilla.samba.org/show_bug.cgi?id=13071
Ferran changed:
What|Removed |Added
CC||pallares.fer...@gmail.com
--- Comment #2 from Fer
https://bugzilla.samba.org/show_bug.cgi?id=8001
--- Comment #2 from Björn Jacke ---
rsync should use pathconf() to find the maximum allowed path length and not
expect to find a OS define like PATH_MAX because this can vary also from
filesystem to filesystem. See
https://pubs.opengroup.org/onlinep
https://bugzilla.samba.org/show_bug.cgi?id=13071
--- Comment #3 from Ben RUBSON ---
Thank you for your feedback Ferran !
I'm not sure about why this patch hasn't been landed yet :)
Regarding benefits of using this option in conjunction with --link-dest.
Well, certainly same benefit as without :
https://bugzilla.samba.org/show_bug.cgi?id=13901
Bug ID: 13901
Summary: Empty quotes adds cwd to SRC directories
Product: rsync
Version: 3.1.3
Hardware: x64
OS: Linux
Status: NEW
Severity: normal
https://bugzilla.samba.org/show_bug.cgi?id=13901
--- Comment #1 from Dave Gordon ---
It probably wouldn't be difficult to spot the case you've identified and change
the behaviour; I suspect you'd just need to change this code around line 2134
of flist.c, in send_file_list() to handle the case of
https://bugzilla.samba.org/show_bug.cgi?id=13912
Bug ID: 13912
Summary: Fix a few typos in rsync.yo
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority:
https://bugzilla.samba.org/show_bug.cgi?id=13913
Bug ID: 13913
Summary: sync a folder with large amount of files
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: normal
P
https://bugzilla.samba.org/show_bug.cgi?id=13913
jief changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=13913
jief changed:
What|Removed |Added
Resolution|WORKSFORME |---
Status|RESOLVED
https://bugzilla.samba.org/show_bug.cgi?id=13913
--- Comment #2 from jief ---
(In reply to jief from comment #1)
My mistake. Previous comment is wrong. Didn't see the --delay-updates option in
my final test.
Bug still remains and it's not a permission problem.
The bug doesn't happen when using
https://bugzilla.samba.org/show_bug.cgi?id=13913
--- Comment #3 from Dave Gordon ---
What filesystems are used at each end?
Also, when you say "hangs", how long have you left it in the "hung" state?
In preparation for trying to reproduce this issue, I created a new directory on
an ext4 filesyste
https://bugzilla.samba.org/show_bug.cgi?id=13920
Bug ID: 13920
Summary: --max-delete and dirs being replaced by symlinks on
source
Product: rsync
Version: 3.1.2
Hardware: All
OS: All
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=13913
--- Comment #4 from jief ---
APFS in one side, ext4 Synology as destination.
I've just made another test. I left it 2 hours. No CPU usage. It just hangs.
Destination doesn't matter. I tried APFS to APFS (selecting an empty directory
as destinatio
https://bugzilla.samba.org/show_bug.cgi?id=13953
Bug ID: 13953
Summary: error message instead of --stats informations (in case
of vanished files), using rsync 3.1.1 and rsync 3.0.9
Product: rsync
Version: 3.1.1
Hardware: x6
https://bugzilla.samba.org/show_bug.cgi?id=13913
--- Comment #5 from Gene ---
I see similar problem using rsync 3.1.3 (both client and server on Arch Linux).
This happened after user duplicated local copy of their Thunderbird profile -
a directory of roughly 42 GB of maildir+ files - so lots o
https://bugzilla.samba.org/show_bug.cgi?id=13974
Bug ID: 13974
Summary: Old max block size isn't allowed in options
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: normal
https://bugzilla.samba.org/show_bug.cgi?id=13982
Bug ID: 13982
Summary: rsync calls exit() from signal handler
Product: rsync
Version: 3.1.3
Hardware: x64
OS: NetBSD
Status: NEW
Severity: major
P
https://bugzilla.samba.org/show_bug.cgi?id=11101
--- Comment #2 from Michal Ruprich ---
I see that the write-devices.diff is in the rsync-patches-3.1.3.tar.gz but this
bug is still in NEW state. Does that mean that the patch should not be used?
What is the relationship between the rsync.git and r
https://bugzilla.samba.org/show_bug.cgi?id=11101
--- Comment #3 from Jason Pyeron ---
the patches repo is where unmerged patches are tracked, stored, and
re-baselined. Not sure how to tickle Wayne Davison to test it. It has worked
very nicely here.
--
You are receiving this mail because:
You ar
https://bugzilla.samba.org/show_bug.cgi?id=11561
--- Comment #2 from Daniel O'Connor ---
What are the prospects for getting this committed?
It works fine on FreeBSD & OSX applied to the latest Samba release and it's
qute handy.
--
You are receiving this mail because:
You are the QA Contact
https://bugzilla.samba.org/show_bug.cgi?id=13991
Bug ID: 13991
Summary: rsync --delete --one-file-system skips deletes after
crossing filesystems on destination.
Product: rsync
Version: 3.1.3
Hardware: All
O
https://bugzilla.samba.org/show_bug.cgi?id=13991
--- Comment #1 from Bruce Arden ---
Created attachment 15235
--> https://bugzilla.samba.org/attachment.cgi?id=15235&action=edit
Commands to demonstrate further problem
set VG to an LVM volumegroup with spare space
On my machine this gives:
...
https://bugzilla.samba.org/show_bug.cgi?id=13735
Sébastien Béhuret changed:
What|Removed |Added
Resolution|WONTFIX |---
Status|RESOLVED
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #10 from roland ---
apparently, what https://www.anchor.com.au/blog/2013/08/out-tridging-tridge/ is
trying to explain and fix (
https://git.samba.org/?p=rsync.git;a=commit;h=de94193353864221280be9fbb6193d92eb133000
) does not fix the is
https://bugzilla.samba.org/show_bug.cgi?id=10051
--- Comment #1 from Haravikk ---
Wow, was about to post basically this same feature, forgetting I'd already
requested it six years ago!
There's definitely still an argument to be made for rsync to handle file names
better when they are invalid on
https://bugzilla.samba.org/show_bug.cgi?id=14076
Bug ID: 14076
Summary: 3.13 - lib/sysacls.h:118:13: error: array type has
incomplete element type 'struct acl'
Product: rsync
Version: 3.1.3
Hardware: x64
OS:
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #11 from Paul Slootman ---
roland: note that unless you explicitly use --inplace, rsync will create a new
file and rename it at the end, so that's going to mess up your zfs snapshot
efficiency anyway.
--
You are receiving this mail be
https://bugzilla.samba.org/show_bug.cgi?id=14076
--- Comment #1 from Jari Aalto ---
Created attachment 15375
--> https://bugzilla.samba.org/attachment.cgi?id=15375&action=edit
Cygwin x64 config.status
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use
https://bugzilla.samba.org/show_bug.cgi?id=14081
Bug ID: 14081
Summary: --copy-command option for specifying custom file
copying behaviour
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Stat
https://bugzilla.samba.org/show_bug.cgi?id=14081
--- Comment #1 from Haravikk ---
Sorry, just occurred to me that rsync already has a similar style option in the
`-rsh` flag for setting a custom remote shell command, so rather than a `find
-exec` style it might make more sense to copy `-rsh` for
https://bugzilla.samba.org/show_bug.cgi?id=14109
Bug ID: 14109
Summary: Support Custom Fuzzy Basis Selection Algorithm
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: normal
https://bugzilla.samba.org/show_bug.cgi?id=14109
--- Comment #1 from Kevin Korb ---
Just a quick thought on a workaround...
It would be trivial to figure out the new name and best old file in a script.
So, you could hard link the best old file to the new file name. Then rsync
wouldn't even nee
https://bugzilla.samba.org/show_bug.cgi?id=14109
--- Comment #2 from Lonnie Best ---
Thanks. Yeah, that's probably what I'll do. I may even write the script where
it does some tasks parallel (running multiple rsync commands at the same time).
The current default "fuzzy-basis-destination-file-sel
https://bugzilla.samba.org/show_bug.cgi?id=12769
--- Comment #4 from Ovidiu Stanila ---
We hit the same issue on a CentOS 6 server (kernel 2.6.32-754.18.2.el6.x86_64),
the sync would break with the following error:
# /usr/bin/rsync --debug=HASH --stats --no-inc-recursive -aHn --delete /app/
:/ap
https://bugzilla.samba.org/show_bug.cgi?id=14126
Bug ID: 14126
Summary: The atomic-rsync script can exit 0 when the operation
failed.
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: N
https://bugzilla.samba.org/show_bug.cgi?id=14126
--- Comment #1 from Paul Slootman ---
Why not exit with $? >> 8?
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change o
https://bugzilla.samba.org/show_bug.cgi?id=14126
--- Comment #2 from Chris Brannon ---
(In reply to Paul Slootman from comment #1)
That was, in fact, my first try.
exit $? >> 8 is recommended for Perl by some sources on the net. However, if
the called program gets a signal, "exit $? >> 8" would
https://bugzilla.samba.org/show_bug.cgi?id=7249
--- Comment #10 from Michal Ruprich ---
Hi,
I think that ideally you should decide what to do with this. This almost 10
years old bug is still here and it seems no one from the rsync developers paid
any attention to this. If you are not planning to
https://bugzilla.samba.org/show_bug.cgi?id=7249
--- Comment #11 from Samuel Henrique ---
This patch has been being applied to the Debian packaging of rsync since 2014
(5 years now).
As Michal Ruprich said, this patch requires the build to be made in a certain
way as it can lead to undefined refe
https://bugzilla.samba.org/show_bug.cgi?id=13445
--- Comment #7 from Ben RUBSON ---
Wayne, let's merge this ?
Many thanks !
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe o
https://bugzilla.samba.org/show_bug.cgi?id=13071
--- Comment #4 from Ben RUBSON ---
Hi Wayne,
Let's review & merge this new feature ?
Thank you very much !
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting th
https://bugzilla.samba.org/show_bug.cgi?id=7249
--- Comment #12 from Samuel Henrique ---
The patch is currently introducing a regression on the target "test" (make
test).
/usr/bin/ld: syscall.o: in function `do_open':
./syscall.c:206: undefined reference to `noatime'
It happens when the target
https://bugzilla.samba.org/show_bug.cgi?id=7249
--- Comment #13 from Samuel Henrique ---
Created attachment 15524
--> https://bugzilla.samba.org/attachment.cgi?id=15524&action=edit
Adds --noatime option for 3.1.3
Updated the patch to fix "make test" with the help of
Paul Slootman.
I'm happy t
https://bugzilla.samba.org/show_bug.cgi?id=7249
Samuel Henrique changed:
What|Removed |Added
Attachment #15524|0 |1
is obsolete|
https://bugzilla.samba.org/show_bug.cgi?id=7249
--- Comment #15 from Michal Ruprich ---
Thanks Samuel,
now I can enable tests during build in Fedora and keep the noatime option as
well. Still though, it would be good to have upstream approval on this :/
--
You are receiving this mail because:
https://bugzilla.samba.org/show_bug.cgi?id=12769
--- Comment #5 from Simon Matter ---
I'm suffering the same problem and was wondering if anyone found a solution or
work around or other tool to do the job?
First I thought maybe it's a bug which is fixed already and tried with the
latest release
https://bugzilla.samba.org/show_bug.cgi?id=14160
Bug ID: 14160
Summary: rsynd in daemon mode should support haproxy proxy
protocol
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=14163
Bug ID: 14163
Summary: RSYNC_SSL_PORT env should be set for invocation of
--rsh command
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status
https://bugzilla.samba.org/show_bug.cgi?id=12769
--- Comment #6 from Dave Gordon ---
The hash table doubles each time it reaches 75% full. A hash table for 32m
items @ 16 bytes each (8 byte key, 8 byte void *data) needs 512MB of memory. At
the next doubling (up to 64m items) it hits the array all
https://bugzilla.samba.org/show_bug.cgi?id=12570
--- Comment #2 from Haravikk ---
I was about to post on basically the same issue, but found this; I use rsync to
do a lot of incremental backups where ZFS or similar isn't an option (not that
common, but still comes up now and then). To guarantee c
https://bugzilla.samba.org/show_bug.cgi?id=14183
Bug ID: 14183
Summary: rsync fails transferring only attributes for file
without write permission
Product: rsync
Version: 3.1.3
Hardware: x64
OS: Mac OS X
https://bugzilla.samba.org/show_bug.cgi?id=14214
Bug ID: 14214
Summary: --report-special=OPS option to return error code if no
data was copied
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
https://bugzilla.samba.org/show_bug.cgi?id=13913
--- Comment #6 from Adam Purkrt ---
I have hit the same. Gentoo Linux
# rsync --version
rsync version 3.1.3 protocol version 31
rsyncing a maildir (as root) with ~36000 files to sshfs mounted dir. strace
tells rsync hangs on select - timeouts for
https://bugzilla.samba.org/show_bug.cgi?id=13913
--- Comment #7 from Adam Purkrt ---
rsyncing to an empty directory went fine; it is the rsync with an already
existing dir that causes the halt.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all
https://bugzilla.samba.org/show_bug.cgi?id=14260
Bug ID: 14260
Summary: leading / added to file name causing file not found
when setting permissions
Product: rsync
Version: 3.1.3
Hardware: All
OS: Linux
https://bugzilla.samba.org/show_bug.cgi?id=14262
Bug ID: 14262
Summary: add continuous sync mode using inotify/fanotify/etc
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: enhance
https://bugzilla.samba.org/show_bug.cgi?id=14262
--- Comment #1 from Paul Wise ---
I note that the lsyncd tool can be used to work around this feature being
missing from rsync. By default it collates filesystem events over several
seconds and then runs rsync to transfer the changes. Giving rsync
https://bugzilla.samba.org/show_bug.cgi?id=14267
Bug ID: 14267
Summary: rsync produces unhelpful errors on remote copy to OS
with different ACL format
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
https://bugzilla.samba.org/show_bug.cgi?id=14315
Bug ID: 14315
Summary: rsync hangs when many errors
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=14315
--- Comment #1 from Mark Vitale ---
Sorry, I gave the wrong commit in my report. I bisected this hang to:
1a2704512a6f6c9bf267042ff8beb50a24e1d057 is the first bad commit
commit 1a2704512a6f6c9bf267042ff8beb50a24e1d057
Author: Wayne Davison
Date
https://bugzilla.samba.org/show_bug.cgi?id=11166
--- Comment #3 from Mark Vitale ---
While debugging a different rsync hang, I have also seen this behavior with
-vvv, and used git bisect to find when it was introduced:
d8587b4690b1987c02c71c136720f366abf250e6 is the first bad commit
intro
https://bugzilla.samba.org/show_bug.cgi?id=14319
Bug ID: 14319
Summary: -M--fake-super --chmod changes the permissions stored
in the xattr
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Sta
https://bugzilla.samba.org/show_bug.cgi?id=7112
--- Comment #1 from Dimitrios Apostolou ---
I agree. I am running rsync with --perms, but I want --fake-super to store the
original permissions in the xattr, and not change the real mode of the
destination file.
What is more, I am trying to force t
https://bugzilla.samba.org/show_bug.cgi?id=12769
--- Comment #7 from Simon Matter ---
I've patches like this to solve our issues:
--- rsync-3.1.3/util2.c.orig2018-01-15 04:55:07.0 +0100
+++ rsync-3.1.3/util2.c2020-03-11 13:07:07.138141415 +0100
@@ -59,7 +59,7 @@
return True;
301 - 400 of 690 matches
Mail list logo
