similar to: Is rsync -avS same as rsync -av --sparse

Hi, -rw-r--r-- 1 root other 5291457346 Sep 6 13:44 rsyncd.log what pattern should I grep for to send you guys more information on rsync failures (server side) Client side messages are: rsync of /oradb/d10 appeared to complete with NON-NOMINAL status (rc=12) at Thu Sep 6 07:33:58 PDT 2012 with the following files reported in output: receiving incremental file list

We are using the standard -av switch. And both filesystems are the same - UFS. /opt/rsync/bin/rsync -av -e "ssh -l root" --delete --exclude-from=/var/scripts/exclude --password-file=/var/scripts/transfer.passwd <username>@<source host>::<source dir>/ /<destination dir> Source system <source host>:<source dir># du -sh * 1K nohup.out 20G

Hi, We use one server from which many other clients download files. This operates in daemon mode over ssh. Is it possible that there is a max number of connections the rsyncd can have on the server? Where is this value set? This is what I see on the client side: rsync: read error: Connection reset by peer (131) rsync error: error in rsync protocol data stream (code 12) at io.c(759)

Please let me know -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20120905/15183c58/attachment.html>

Hi all, I'm writing a script that uses rsync to sync 2 dirs on C7. I noticed a strange behaviour. I have 2 dir: src and dest. In src dir I generate a testfile with "dd if=/dev/zero of=testfile bs=1M count=100" and when I run "du -h testfile" I get the correct result. Then I sync src/ to dest/ using "rsync -avS? src/ dest/", all ok but when I run "du -h

rsync fails on some directories while on others it works without issue. Here are the inportant items: On theserver from which directories are being copied: more /etc/rsyncd.conf <snip> [abcd] path = /xyz/abcd comment = abcd uid = 0 gid = 3 read only = yes list = no auth users = test-abcd secrets file = /etc/rsyncd.passwd strict modes = true hosts allow =

Hi, I usually run "rsync -av" so I can see all the files that have been modified. However, "rsync -av" always claims to be updating write protected directories, even when they have not been changed. I do not understand why. Here is an example using rsync version 2.6.3 on FreeBSD 5.3. I get similar results with rsync 2.6.0 on Gentoo Linux. -------- $ mkdir dir0 $ touch

Il 15/01/20 17:51, Jon Pruente ha scritto: > On Wed, Jan 15, 2020 at 10:18 AM Alessandro Baggi < > alessandro.baggi at gmail.com> wrote: > >> I made several test to see what happens and noticed that removing -S >> (--sparse) from rsync command problem does not occour. >> In another test, thinking about a problem on 0ed file, I tried file >> generation using

Hi, i'd like to rsync some image files from virtual hosts each night. The image files are between 50GB and 400GB big. I thought rsync would be the appropriate solution because it just transfers the differences, not the whole file. But nevertheless rsync takes hours. The images aren't much modified over the day, i would expect just some tens of megabyte needed to be transfered. I have the

Hi all! There is a need to copy sparse files (precisely VMware disk images) with rsync. For that purpose I'm using the -S (--sparse) option and they are copied just fine (the check sums of the original and file at destination are the same). However, as it is said in the manual: [quote] -S, --sparse Try to handle sparse files efficiently so they take up less space on the destination.

issue is with 3 directories. Is it possible that some files in those directories are "open", being written to etc that causes the issue? connection reset by peer is the message we get. This is rsync in daemon mode on TCP port 873 -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugzilla.samba.org/show_bug.cgi?id=3925 Summary: rsync is unable to sync large (approx 4G) sparse files Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=13317 Bug ID: 13317 Summary: rsync returns success when target filesystem is full Product: rsync Version: 3.1.2 Hardware: x64 OS: FreeBSD Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=11651 Bug ID: 11651 Summary: Can we allow --inplace and --sparse to coexist when --whole-file is in play? Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core

Hi, I'm using rsync with --link-dest to do backups. I don't have any sparse files, but someday I might. Should I be using --sparse? I notice that -S is not implied by -a. This makes me suspicious that --sparse is not (yet?) suitable for general purpose use. There also seem to be outstanding bugs related to --sparse. Thanks. Karl <kop at meme.com> Free Software: "You

Hi, I'm trying to setup an rsync daemon such that I can synchronize my home pc (or other remote system) with my pc at work. I'm fairly new to linux and am just starting to learn its amazing possibilities. I followed an online toturial to create a rsyncd.conf file which reads: #motd file = /etc/rsyncd.motd log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file =

I have a 5.5GB file, mostly sparse. Tar performs far[!] better than rsync. I have no ideas yet, so just an FYI as to current state. FreeBSD 8.1 i386 zfs Yes, I know the blocks used differs but don't know why yet, could be just how zfs does things or related to the large amount of sparseness. There are no media errors, CPU/IO load or anything like that and the source and dest paths are on the

So I was transferring a 2GB virtual machine disk image image over a slow wireless link. Of course I used --sparse, to keep the image small on the destination end as well as on the source end. Much to my surprise, I noticed that the transfer took a long time even when it got past the first 0.5GB of actually-populated file. A little sleuthing with strace revealed that the source rsync was dutifully

This is the case - mounted Inetpub's windows-webserver on /mnt/web1 /mnt/web2, etc. - rsync this to local dir: rsync -av --delete /mnt/web1 /mass/kuurne/day rsync -av --delete /mnt/web2 /mass/kuurne/day etc.. - when logged in, everything works (I do see some errors about non-existing files, but rsync won't stop. When used this command in cron 00 01 * * * rsync -av --delete

Hi Bas, I'm not sure if this is of interest, but I also had issues with VM disk-image sparse-files (in my case KVM, rather than VMWare), which I've now resolved. http://www.finalcog.com/rsync-vm-sparse-inplace-kvm-vmware All the best, Chris Dew. P.S. Apologies for any breach of etiquette - I could not see Bas' email address on