Re: rsync sends -C and -x options silently
On Wed, May 16, 2018 at 10:04 AM Anand Buddhdev via rsync < rsync@lists.samba.org> wrote: > This newer rsync version appears to be sending -C and -x options to the > server, even though they are not set on the client side. > It's not. What it is doing is sending information in the -eSTRING option that tells the server some extra compatibility info that can apply to even older protocol versions. In the --server -e arg's string the 'x' and 'C' flag characters can be present these days, and more internal flags may be added in the future. So, it sounds like you just need to fix your option parsing to recognize that -e is followed by a free-form string arg. Also note that when --server is specified, the -e arg has a different meaning than it does to the client, so don't be confused by the -e option in the manpage. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: [Bug 5478] rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)
On 17/04/18 17:47, just subscribed for rsync-qa from bugzilla via rsync
wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=5478
>
> --- Comment #34 from David Nelson ---
> FYI. Although when rsync ver. 3.0.9 is called in Ubuntu 12.04LTS to "push"
> files to the server, e.g.,
>
> rsync / server::Backups/
>
> it fails with the error:
>
> rsync error: error in rsync protocol data stream (code 12) at io.c(441)
> [sender=3.0.9 [NB server rsync version is 3.1.0 running in Ubuntu 14.04LTS]
>
> However, curiously, when issued as a "pull" from the server as:
>
> rsync client::Sharetobackup//Backups/
>
> it succeeds.
>
> Furthermore, pushes from the client work when issued one-letter-as-a-time;
> e.g.,
>
> for i in {A..Z}; do \
> rsync /${i}* server::Backups/ \
> done
>
> I discovered this while trying to isolate which, if any, of the files were
> causing it to choke. Turns out none of them were, but identifying them all
> with
> a wildcard * was.
Hi,
did you mean to add this comment to Bug 5478, which had been closed for
~5 years? It looks like it should belong to some other (more recently
active) bug - maybe 2957, 12732, or 13109?
.Dave.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 13433] out_of_memory in receive_sums on large files
https://bugzilla.samba.org/show_bug.cgi?id=13433 --- Comment #1 from Dave Gordon --- Maybe try --block-size=10485760 --protocol=29 as mentioned here: https://bugzilla.samba.org/show_bug.cgi?id=10518#c8 -- 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 options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 13433] out_of_memory in receive_sums on large files
https://bugzilla.samba.org/show_bug.cgi?id=13433
--- Comment #2 from Kevin Day ---
(In reply to Dave Gordon from comment #1)
It looks like that's no longer allowed?
rsync: --block-size=10485760 is too large (max: 131072)
rsync error: syntax or usage error (code 1) at main.c(1591) [client=3.1.3]
#define MAX_BLOCK_SIZE ((int32)1 << 17)
if (block_size > MAX_BLOCK_SIZE) {
snprintf(err_buf, sizeof err_buf,
"--block-size=%lu is too large (max: %u)\n",
block_size, MAX_BLOCK_SIZE);
return 0;
}
OLD_MAX_BLOCK_SIZE is defined, but options.c would need to be patched to allow
looser block sizes if protocol_version < 30
--
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 options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 13433] out_of_memory in receive_sums on large files
https://bugzilla.samba.org/show_bug.cgi?id=13433 --- Comment #3 from Kevin Day --- Just adding --protocol=29 falls back to the older chunk generator code and automatically selects 2MB chunks which is enough to at least make this work without a malloc error. -- 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 options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
