similar to: Rsync --delay-updates takes a long time

I'm just not entirely clear from the man page.. does the timeout start counting from the last communication, or does it start counting from the beginning of the transmission? also, if the server is set to timeout at, say, 300s, and it's busy moving stuff around but not talking to the client, does the timeout start counting? So if it takes 300s to move a file out of a partial-dir

Hey folks, I did some googling on this but did not come up with much. I'm using rsnapshot which uses rsync, and I notice some pretty long pauses in the xfers as you can see on this graph from "munin". THe machine in question right at the moment is doing nothing but rsyncing ( rsnapshoting ) some 12T of NAS storage to local disk, so there is nothing else going on at all.

I''m running 2.6.6 on a red hat EL3 system. using the following command, rsync -rlptDvzL --stats --include=a/ --include=a/dir/ --include=a/dir/symlink/ --include=a/dir/symlink/dir2/ --include=a/dir/symlink/dir2/dir3/ --exclude=''**'' /export/stuff remote::stuff I expect the "symlink" (which is really a symbolic link to a directory) to be preserved on the

Hello, rsync list folks, Recently, rsyncs abort during busier times of the day, although they run error-free during non-busy hours. Problem 1 - Many rsyncs abort these errors: Read from remote host www.xxx.yyy.zzz: Connection reset by peer rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: connection unexpectedly closed (3929920 bytes received so far)

If your goal is to reduce storage, and scanning inodes doesnt matter, use --link-dest for targets. However, that'll keep a backup for every time that you run it, by link-desting yesterday's copy. Y end up with a backup tree dir per day, with files hardlinked against all other backup dirs. My (and many others) here's solution is to mv $ancientbackup $today; rsync --del

I want to use rsync with a cloud based rsync provider to do off-site backing up of a large (1TB) dataset which consists of 32 million+ files spread out in 300 directories. So the amount of files in any one directory can be quite large (upwards of 2 million). Rsync doesn't seem to cope with this well - even doing local copies in a directory with several thousands of files takes a long time to

Hi Friends, I am using rsync to copy data from Production File Server to Disaster Recovery file server. I have 100Mbps link setup between these two servers. Folder structure is very deep. It is having path like /reports/folder1/date/folder2/file.tx, where we have 1600 directories like 'folder1', daily folders since last year in date folder and 2 folders for each date folder like folder2

rsync -avnp remote::gif/ `find /home/www/html/ -maxdepth 1 -name "*.[j,g][pg,if]*"` /tmp/ If I run this on the local machine, the rsync server, it takes this long: ---> root@server (0.34)# time find /home/www/html/ -maxdepth 1 -name "*.[j,g][pg,if]*" -type f /home/www/html/comparestores_2.jpg /home/www/html/home.jpg /home/www/html/comparestores_3.jpg

I have a migration "x" that when it runs self.up it adds a new column to a table, and of course when self. down is run it deletes said table... After I ran this migration I continued to work and in the process added a couple other migrations. After a while I realized that the column migration "x" created was a mistake and I no longer need it. So I ran rake db:migrate:down

https://bugzilla.samba.org/show_bug.cgi?id=5977 Summary: --delay-updates --partial-dir Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: gb43254@vip.sina.com

Hello, We have MySQL running as a master which is replicating to a single slave server. We are, however, considering what is required when a 'disaster' of some sort happens to either server. By disaster, this could be some event which requires the entire server to be rebuilt, and which would usually include restoring from nightly backups directories such as '/var/lib/mysql' and

Hi, I did the zpool import/export performance testing on opensolaris build-134: 1). Create 100 zfs and 100 snapshots, then do zpool export/import export takes about 5 seconds import takes about 5 seconds 2). Create 200 zfs and 200 snapshots, then do zpool export/import export takes about 80 seconds import takes about 12 seconds 3). Create 300 zfs and 300 snapshots, then do

Hi, recently I had to instal a new raid storage system for our central fileserver. It is connected by iscsi (1Gbit) and the fielsystems mounted are 400GB and 1TB and ext3. curretly about 400 GB are used by 1.5 Mio files. I turned quota on and did a quota check. BUT on reboot the system crashes/hangs during 'turning off quotas' This message shows up about 30++ sec after the shutdown ...

I have an X4500 fileserver (NFS, Samba) running OpenSolaris 2008.05 pkg upgraded to snv_91 with ~3200 filesystems (and ~27429 datasets, including snapshots). I''ve been encountering some pretty big slow-downs on this system when running certain zfs commands. The one causing me the most pain at the moment is setting the "sharenfs" property on a filesystem takes a little under 7

Hi, I am using guestfish, and found subcommand "launch" took about 20 seconds to finish for a 4GB disk image. Is there any way to improve the performance? Thanks! Regards, Qian

http://bugzilla.mindrot.org/show_bug.cgi?id=1005 Summary: installing openssh on AIX takes a long time when there are many users Product: Portable OpenSSH Version: 4.0p1 Platform: All OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo:

When I change a setting via the web interface on a polycom 500, it takes minutes to allow access through the web interface again. Any idea why it is so slow? Chris Mason

Hi, try to use virtio instead... Atte. Daniel Romero P. On Thu, May 10, 2018 at 3:53 PM, Ihar Hrachyshka <ihrachys@redhat.com> wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed, which for some buggy images like cirros may slow down boot > process

On 05/10/2018 02:53 PM, Ihar Hrachyshka wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed What is your definition of "becomes ready"? Are you looking at the output of "ip link show" in the guest? Or are you watching "brctl

On Thu, May 10, 2018 at 11:53:23AM -0700, Ihar Hrachyshka wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed, which for some buggy images like cirros may slow down boot > process for up to 1 minute [2]. If we switch from e1000 to virtio, the > link is