similar to: [Bug 10677] New: external zlib broken after update to 3.1.1 on FreeBSD

Displaying 20 results from an estimated 1100 matches similar to: "[Bug 10677] New: external zlib broken after update to 3.1.1 on FreeBSD"

2015 Jul 04
0
[Bug 11378] Please add a '--line-buffered' option to rsync to make logging/output more friendly with pipes/syslog/CI systems/etc.
https://bugzilla.samba.org/show_bug.cgi?id=11378 Nathan Neulinger <nneul at neulinger.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #2 from Nathan Neulinger <nneul
2017 Jul 28
0
[Bug 12940] New: rsync: -C/--cvs-exclude does not ignore SCM ignore files (patch)
https://bugzilla.samba.org/show_bug.cgi?id=12940 Bug ID: 12940 Summary: rsync: -C/--cvs-exclude does not ignore SCM ignore files (patch) Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core Assignee:
2017 Oct 06
2
rsync does hours of "fake-work" after failure
Hi, I just stepped on a strange and very annoying bug in rsync-3.1.0 as shipped with SuSE Linux Enterprise 12, but verified the bug also with rsync-HEAD-20170123. I tried to copy some of my movie collection to a usb disk that our TV could read, so it was formatted with vfat. I forgot that vfat can't handle files > 4 GB, and some of the movies were larger. rsync worked for 3 hours copying
2019 Nov 04
0
Recent inability to view long filenames stored with scp via samba mount
On Sun, Nov 03, 2019 at 06:37:57AM -0500, Michael Lueck via samba wrote: > I have Samba shares mounted to my Linux workstation. Mostly I access files on the Samba server over the Samba mount. I use mount.cifs to bring up these mounts. > > For a couple of special cases, I use scp to transfer files between the > server and workstation. Special characters in filenames give sending them
2018 Nov 07
0
Avoiding constant HDD access
On Wed, 7 Nov 2018 12:21:17 +0100 Reindl Harald via samba <samba at lists.samba.org> wrote: > > > Am 07.11.18 um 12:07 schrieb Rowland Penny via samba: > > On Wed, 7 Nov 2018 11:44:28 +0100 > > Reindl Harald via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 07.11.18 um 09:54 schrieb Rowland Penny via samba: > >>>
2018 Nov 07
2
Avoiding constant HDD access
Am 07.11.18 um 09:54 schrieb Rowland Penny via samba: > On Wed, 7 Nov 2018 05:45:45 +0300 > Albert Berger via samba <samba at lists.samba.org> wrote: > >> I'm running a Samba server on Raspbian and observing that Samba >> during idle periods is constantly (every minute) writing to HDD >> (maybe doing some journaling?) what causes the HDD to constantly spin
2019 Nov 03
0
Recent inability to view long filenames stored with scp via samba mount
On 03/11/2019 11:37, Michael Lueck via samba wrote: > Greetings Samba team, > > It has been a long time since I needed to ask a Samba technical question. > > Server and workstation are both running the latest Samba packages via > Ubuntu 16.04 LTS. I recently applied the security updates... actually > that was yesterday I applied them. > > >> samba
2014 Jun 11
0
Progress indication refreshes too often with --info=progress2
Hi there: I am testing rsync with a large number of small files. I am using 'tee' to keep the log, and I noticed that the log file was growing very quickly. It seems that the progress text refreshes too often: building file list ... ?0 files... ?100 files... ?200 files... ?300 files... ?... ?5.53G? 95%??? 8.50MB/s??? 0:10:20 (xfr#478709, to-chk=9/537759) ?5.53G? 95%??? 8.50MB/s???
2018 Nov 07
4
Avoiding constant HDD access
Am 07.11.18 um 12:07 schrieb Rowland Penny via samba: > On Wed, 7 Nov 2018 11:44:28 +0100 > Reindl Harald via samba <samba at lists.samba.org> wrote: > >> >> Am 07.11.18 um 09:54 schrieb Rowland Penny via samba: >>> On Wed, 7 Nov 2018 05:45:45 +0300 >>> Albert Berger via samba <samba at lists.samba.org> wrote: >>> >>>>
2014 May 01
4
[Bug 10580] New: Total file size reported wrong with --stats --info=progress2
https://bugzilla.samba.org/show_bug.cgi?id=10580 Summary: Total file size reported wrong with --stats --info=progress2 Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org
2018 May 08
4
[Bug 13423] New: Checksum option does not work as expected when append-verify is used
https://bugzilla.samba.org/show_bug.cgi?id=13423 Bug ID: 13423 Summary: Checksum option does not work as expected when append-verify is used Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core
2019 Nov 03
4
Recent inability to view long filenames stored with scp via samba mount
Greetings Samba team, It has been a long time since I needed to ask a Samba technical question. Server and workstation are both running the latest Samba packages via Ubuntu 16.04 LTS. I recently applied the security updates... actually that was yesterday I applied them. > samba (2:4.3.11+dfsg-0ubuntu0.16.04.23) xenial-security; urgency=medium > > * SECURITY UPDATE: client code can
2018 Apr 02
1
Much improved speeds of rsync via SSH - something to consider
Dear rsync devs, I recently concluded a bug hunt to trace why my rsync-ing to an SBC was much slower than the corresponding iperf3-reported speeds. To give a concise summary of the situation, in slow wifi links using SSH with ProxyCommand tremendously speeds up things: $ dd if=/dev/urandom bs=1M count=50 of=sample.data 50+0 records in 50+0 records out 52428800 bytes (52 MB, 50
2016 Jan 21
0
Why is my rsync transfer slow?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First, don't use -z on a local copy. It will only make rsync slower for no reason at all. Second, 45 million files means 90 million calls to stat(). This will take a while even if nothing needs copying. On 01/21/2016 03:20 AM, dbonde+forum+rsync.lists.samba.org at gmail.com wrote: > I run a rsync job transferring about 45 million
2015 Apr 14
1
The --inplace is very different from the behaviour of --partial when resuming a complex case transfer.
Hi all, >From the manpage of rsync, I can see the following descriptions: --inplace The option implies --partial (since an interrupted transfer does not delete the file) So I do the following testings on the `--inplace' and `--partial' for resuming a file with the following steps: 1- rsync ftp.cn.debian.org::debian/dists/wheezy/main/binary-amd64/
2020 Aug 11
2
Meaning of "failed verification -- update retained (will try again)."
Hi, I see some warnings like the following. Could anybody explains what they mean? Thanks. 19/31274477.pdf 257,169,119 0% 1.26MB/s 0:03:15 (xfr#121, to-chk=848309/1043298)WARNING: 18/32281577.pdf failed verification -- update retained (will try again). WARNING: 19/28879866.pdf failed verification -- update retained (will try again). -- Regards, Peng
2010 Jan 11
1
The patch write-devices.diff (rw-devices.diff) fix
Hello, I faced the problem of synchronization block devices and found the patch write-devices.diff by Darryl Dixon, that went trough this mailing list http://lists.samba.org/archive/rsync/2009-October/024037.html Unfortunately the patch was one flaw for me. It doesn't improve performance of synchronization. When I tried to test it using something like: ./rsync
2016 Jan 21
4
Why is my rsync transfer slow?
I run a rsync job transferring about 45 million files/approximately 1.8 TB data (a Mac OS X Time Machine backup) over a 100 MBit connection. I use rsync 3.1.1 from MacPorts (I first tried the built in rsync, version 2.6.9, since it has a Mac OS X specific cache parameter, but it ran out of memory) with the following parameters % rsync -HzvhErlptgoDW --stats --progress --out-format="%t %f
2015 Jul 27
8
[Bug 11414] New: rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)
https://bugzilla.samba.org/show_bug.cgi?id=11414 Bug ID: 11414 Summary: rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1) Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5
2015 Jan 26
1
[Bug 11075] New: Shouldn't --inplace fail immediately if it can't make files?
https://bugzilla.samba.org/show_bug.cgi?id=11075 Bug ID: 11075 Summary: Shouldn't --inplace fail immediately if it can't make files? Product: rsync Version: 3.1.0 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core