Re: Data corruption check
At 08:12 19.09.2007 -0700, Keith Lofstrom wrote: On 9/18/07, Fabian Cenedese [EMAIL PROTECTED] wrote: I was wondering what happens if a file that is regularly synched but seldom changes gets corrupted in the copy. On Wed, Sep 19, 2007 at 09:23:28AM +0200, Fabian Cenedese wrote: I was asking because I'm responsible for our backups. The current solution with rsync works nicely. While the RAID storage also monitor the HD's SMART state I was still wondering about a way to detect otherwise unknown data corruption. I run rsync inside of dirvish (www.dirvish.org) for automated backups. I also run osiris (osiris.shmoo.com) which scans for modified files, both checking the metadata and a hash of the actual data, finding all changes relative to a database on a central osiris server. We already have a backup system that creates incremental backups as well as mirroring the file server as well as the backups to a second RAID. I think the osiris is a bit overkill for our application. But thanks for the info. bye Fabi -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: PATCH for 2.6.9 to fix logging of daemon stats
Hi Wayne, I'm using 2.6.9 with the daemon-stats.patch you had send a few months back (attached). I have noticed something strange though: I ran a dry run WITH the --exclude-from=FILE argument: sent 39440 bytes received 22 bytes 15784.80 bytes/sec total size is 569895385 speedup is 14441.62 (Thats approx 569 MB total size) ...followed immediately by a dry run WITHOUT the --exclude-from=FILE argument: sent 1576836 bytes received 126502 bytes 25614.11 bytes/sec total size is 30053499099 speedup is 17643.88 (Thats approx 30GB total size) The exclude-from list contains files that amount to a few GB, but definitely not to bring down to 569MB.. so that value in the first case is definitely wrong. Has there been a patch for this? Thanks again Julian - Original Message - From: Wayne Davison [EMAIL PROTECTED] To: Julian Pace Ross [EMAIL PROTECTED] Cc: rsync@lists.samba.org Sent: Thursday, September 20, 2007 2:05 AM Subject: Re: PATCH for 2.6.9 to fix logging of daemon stats On Wed, Sep 19, 2007 at 10:17:52PM +0200, Julian Pace Ross wrote: I may be wrong, but it seems that when total size is more than bytes (int32), the total size is still displayed wrongly in the daemon logs when the daemon is the receiver. What version are you talking about? The CVS version has had this fixed for quite some time now (using write_varlong(), which handles 64-bit numbers). ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html daemon_stats.patch Description: Binary data -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Installation guide of Rsycn
Hi All, Is there anyone where can I get the installation guide of Rsync for installing a HP UX B11.11 server, please advice. Thank you. From: Eng -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in IPC Code (code 14) at main.c(669) [receiver=2.6.9cvs]
Hi, I got the issue solved after doing some analysis.. I am not closing a file handle in one case and the same process is invoking rsync command.. In the long run the process is running out of file descriptors and causing the failure.. Suresh Kumar wrote: Hi, I am using rsync 2.6.9 and recently I got a error with the setup. I searched in the forums but I couldn't find much clues on this. Once I restarted the rsync daemon and rerunning the job didn't gave any errors further. I also tried to reproduce the issue for much details. But I couldn't do that even after hours. The rsync log says opening tcp connection to 172.21.3.148 port 874 opening connection using --server --sender -vvulgtprxz --timeout=38400 --safe-links . job_27825 receiving file list ... 23 files to consider rsync: pipe failed in do_recv: Too many open files (24) rsync error: error in IPC code (code 14) at main.c(669) [receiver=2.6.9cvs] If anybody has already faced similar kind error let me know what was the issue and how this has been suppressed. Regards, Suresh -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- View this message in context: http://www.nabble.com/error-in-IPC-Code-%28code-14%29-at-main.c%28669%29--receiver%3D2.6.9cvs--tf4421785.html#a12811047 Sent from the Samba - rsync mailing list archive at Nabble.com. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
