similar to: DO NOT REPLY [Bug 3485] New: rsync uses more space in destination even with -S specified

https://bugzilla.samba.org/show_bug.cgi?id=5373 Summary: rsync uses more space in destination even with -S specified Product: rsync Version: 2.6.2 Platform: PA-RISC OS/Version: AIX Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

i'm running on vmware system and HP proliant DL360 G5 servers on wmware, on boot i have the following message: ----------------------------- Applying Intel Microcode update: don't know to make device "cpu/microcode" [OK] ----------------------------- and on a HP proliant DL360 G5 server , on boot i have too the following message: ----------------------------- Applying

After yum upgrade, the new CentOS5 kernel [ kernel-2.6.18-92.1.1.el5.i686 ] crashes each time early in boot process on Compaq ProLiant 3000 with dual Pentium3 CPU (600 MHz, CPU0: Intel Pentium III (Katmai) stepping 03, CPU1 the same). I get kernel panic at powernowk8_init+0x05e/0x1c3. The previous kernel [ kernel-2.6.18-53.1.21.el5.i686 ] seems to work fine. I am wondering if anyone has met

I am enclosing scripts and config files to generate exact copy of CentOS 5.0 i386 installation DVD image, that is CentOS-5.0-i386-bin-DVD.iso if you have CD images for i386. If there is interest I can post the same for x86_64. Please follow README files for instructions. All the scripts are GPL. SHA1 for attached files: 439f7b0bd50722388a2836eedafeb1c227f97385 *00_README.txt

I have seen that file ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-3.4p1.tar.gz is continuosly changing. This seems strange to me as I expected it should be a 'frozen' file; The signature and diff file are still dated Jun 26. I am wondering whether this is intentional. Best regards, Wojtek

https://bugzilla.samba.org/show_bug.cgi?id=5458 Summary: -a -X throws error when processing fifo, even if --no-D is specified Product: rsync Version: 3.0.1 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi! I am running rsync 2.6.4 (on Debian sarge) and I am experiencing a strange behaviour. I am trying to create an identical filetree on the same filesystems with the single files being hardlinks to the source like this: rsync -vaH --progress --delete --stats --numeric-ids -x --link-dest=/path/to/filetree/ /path/to/filetree/ /path/to/current/ /path/to is one filesystem. This creates hardlinks

https://bugzilla.samba.org/show_bug.cgi?id=3594 Summary: --delete doesn't delete destination files that don't exist at the source Product: rsync Version: 2.6.7 Platform: PPC OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=7337 Summary: sparse files not equally sparse on destination Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: brian at

https://bugzilla.samba.org/show_bug.cgi?id=5455 Summary: destination files with resource forks now have current mtime Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hello, I have written a little script that's would email me all errors. rsync -vah --delete --stats <sources> <destination> > /var/log/sauvegarde/listoffile.log 2> /var/log/sauvegarde/errors.log My problem is i want to have the stats in my mail. Is it possible to redirect --stats to STDERR. I have tryed to do this : /---

https://bugzilla.samba.org/show_bug.cgi?id=4080 Summary: rsync can't find basis dirs with -n and nonexistent destination Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=4786 Summary: deletes files in parent directory when destination directory doesn't exist Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=5223 Summary: Options to limit --one-file-system at the source or destination. Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=4985 Summary: --list-only shows implied dirs even with --no-implied- dirs Product: rsync Version: 3.0.0 Platform: Other OS/Version: Linux Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=5528 Summary: rsync deletes files it shouldn't even look at! Product: rsync Version: 3.0.3 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=3549 Summary: rsync applies umask to some directories even when a default ACL takes effect Product: rsync Version: 2.6.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=8838 Summary: rsync daemon chooses wrong destination place if space and the module name is part of it Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=5298 Summary: xattrs and acls do not work well together along with fake-super, even worse on XFS Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Is it normal for rsync to take 3 hours on this transfer? Number of files: 27419348 Number of files transferred: 19501 Total file size: 185.39G bytes Total transferred file size: 195.92M bytes Literal data: 195.68M bytes Matched data: 241.09K bytes File list size: 402.01M File list generation time: 0.561 seconds File list transfer time: 0.000 seconds Total bytes sent: 600.61M Total bytes received: