similar to: hard-link reference error when trying to delete

Hi, Kevin. Thank you for the suggestion. It triggered a memory that I had set some restrictions on this rsync copy a while back. Sure enough, in ~/.ssh/authorized_keys: command="rsync --server -vulogDtpre.iLsfxC --timeout=600 --bwlimit=5120 . dest" ssh-rsa Tacking on --delete in the appropriate spot fixed the issue. That's a big whoops on my part. :-) Appreciate the pointer.

Have you tried doing the clean shell test? ssh -i /path/to/key user at remote.server.com true > testfile if testfile isn't 0 bytes then whatever is producing the data that ended up in there is your problem. On 08/15/2017 04:13 PM, jared via rsync wrote: > Hello, all. I've encountered an odd error that I haven't been able to > identify and resolve myself. Hoping someone

When attempting to sync multiple sources to a single area, /fs/lib# ls ./ ../ bin/ founder/ skill/ var/ I want to combine these four rsyncs /usr/local/bin/rsync --exclude '.snapshot' --stats -v --bwlimit=1024 --delete -atz 'host::lib/bin' . /usr/local/bin/rsync --exclude '.snapshot' --stats -v --bwlimit=1024 --delete -atz 'host::lib/var' .

I'm using 2.6.3pre1 to transfer a rather large Debian archive (126GB, more than 30 million files). It contains about 450 daily snapshots, where unchanged files are hardlinked between the snapshots (so many files have hunderds of links). It's been running for some time now, and I found that while it's far from done, it's already used 165GB on the receiving end. Investigation shows

Sorry, it seems I have only replied to Lakhdar, not to the newsgroup. Below is my reply to Lakhdar, and I would like to make it more clear now, using some pseudo values for simplicity: I read bytes 1 to 124 from my encoded spx file. I decode themt and get the values: ---Frame 1---- -293 -8234 2134 17 ---Frame 2---- -9323 -732 189 2329 Both frames are just perfect as I need them. But now when I

I have Rsync working ok, backing up some server directories onto another server each evening. If I do an rsync back up of a directory - called "test", for example - and in the "test" directory there is a file called "testfile", it gets backed up OK. However, if that file, "testfile" gets deleted from the original "test" directory, when I run

Hello Everyone: I've been trying to get rsync using --bwlimit using openssh for transport without success. Here's what I get: % rsync --bwlimit=20 from.com:/dir/file.txt /dest user@from.com's password: **** rsync: unrecognized option `--bwlimit=20' unexpected EOF in read_timeout I tried specifying ssh transport using both the -e option and by setting the RSYNC_RSH

Skipped content of type multipart/signed-------------- next part -------------- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

http://bugzilla.mindrot.org/show_bug.cgi?id=552 Summary: broken reference from scp.c Product: Portable OpenSSH Version: 3.6p1 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: dh at

My impression when running with --bwlimit in combination with compression -z is that the speed to the filesystem is limited to the value given in --bwlimit. This must be contrary to the intention with --bwlimit. David

Hi, I have two issues with the --bwlimit parameter to rsync which are not mentioned in the FAQ (please correct me if I am wrong): 1. When both an rsync client and an rsync daemon specify the --bwlimit parameter, the client's value overrides the server's value. This could be used in a DOS attack if the client uses a larger value than the server intended. The documentation also is

I didn't get any responses to my previous post "Wine broken on Samba shares due to colon ":" filenames" so I am re-posting with a subject to reflect what I now believe to the the root cause of my problems. I recently changed from mounting my home directory using NFS to mounting with CIFS via the pam module pam_mount.so. It turns out that I am having problems with many

Hi list, I couldn't find anything related to this, on mailing lists or even bugzilla, so here it is. A problem with this combination exists in the new 2.6.3 where the bwlimit code got rewritten and is not present at <= 2.6.2. The problem is that on io.c:882 bwlimit_writemax is also used to control the bandwidth, but it is not initialized for the daemon mode. At options.c:772 you can see

[I'm not subscribed, please CC me on replies] Some time after 2.6.0 the --bwlimit code was enhanced, but the code now doesn't work anymore when you set the bandwidth limit for the daemon and generates error log entries like: 2005/01/13 08:17:03 [29636] rsync: writefd_unbuffered failed to write 12 \ bytes: phase "unknown" [receiver]: Success (0) 2005/01/13 08:17:03 [29636]

Has anyone noticed that the --bwlimit doesn't really work? I have MRTG stats happening, and on a 128Kbps circuit, an rsync with the following syntax takes up the whole line. $ rsync -avz -e ssh localfiles.tar.gz user@remote:/path/to/file/arch Any ideas? It's on an OpenBSD box going to a FreeBSD box. Both are 2.4.6. -#0

Hello! I cant get the bwlimit option working right. If i set this option over 400 kbyte per sec i still only get 400kbyte per sec, whether wich value i set. I try this option with a 100MB big file. I use a debian stable System with rsync version 2.5.6cvs protocol version 26. Can someone tell me how i can this get working? thx Rene dpkg -l "rsync*" ii rsync 2.5.5-0.1 fast remote

I am doing some benchmarking of rsync. I am using the --bwlimit= option to throttle down rsync to predict its operation over slow communications links. I am using rsync 2.6.2 from the release site without any patches. I downloaded the release rather than pull from the CVS tree. I have 2 servers "wilber" (the remote archive) and "judy" (the local archive) connected with a gig

Does "bwlimit" option really work on rsync locally? We have one type of harddisk and want to slow down rsync I/O on disk because I don't want the disk head gets too hot. While I'm trying to use --bwlimit option, it looks the rsync speed was slowed down, but iostat is not improved at all. In both case the block written speed is increased by the same amount. How could I really

I'm looking at using Rsync to synchronize 600 Windows servers across the country to a central location. I'll be synchronizing about 15-20 gigs of data, but the vast majority will never change... every now and then, we would have to add new files, ranging in size from a few bytes to 1.5GB. Each server is on a slow frame relay connection and will be limited to 3KB/sec. The connections are

Hi everybody, I am using Cygwin rsync/ssh to synchronize my files from my home computer to my server. I raised a question on the Cygwin list as well, but thought this list would be appropriate too. The issue is that the CPU on the sending side is fully allocated by rsync/ssh (both taking 50%) during a file transfer. This is the command I use: rsync -e ssh * <user>@<server>:/data