CygWin support for 2Gb files (rsync too!)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi to the list. Yesterday the new test release of CygWin (1.5.3) became stable and with that many cygwin packages, rsync-2.5.6-3 (compiled for cygwin 1.5.x) among them. This means that everyone had better open http://cygwin.com/setup.exe and upgrade it all, and get the new 64-bit file pointers feature. Please notice that cygwin-1.3 binaries can work with cygwin-1.5 library, but not the reverse. Better yet would be to use newly compiled binaries with the new library, to be both sure that it works and it supports 64-bit files. Almost each package in the cygwin distribution has been upgraded. Good download, ~ Lapo - -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAj9VtVoACgkQaJiCLMjyUvu+VwCg0E1mj5uxpDtG1MPri2hFDde3 DVgAoMI544ozuXsYqgHMY+ESzc7E3vSX =zMpZ -END PGP SIGNATURE- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rezultatele scanãrii cu RAV AntiVirus
RAV AntiVirus for Linux i686 version: 8.3.2 (snapshot-20020108) Copyright (c) 1996-2001 GeCAD The Software Company. All rights reserved. Registered version for unlimited domains. Running on host: mail.dntcj.ro Fiºierul (part0002:your_document.pif) ataºat email-ului trimis de cãtre [EMAIL PROTECTED] pentru [EMAIL PROTECTED], , (cu subiectul Re: Your application), este infectat cu virusul Win32/[EMAIL PROTECTED] Fiºierul nu a putut fi curãþat. Mesajul-ul nu a fost trimis deoarece conþinea cod periculos. Scan engine 8.11 () for i386. Last update: Tue Sep 2 16:32:02 2003 Scanning for 81709 malwares (viruses, trojans and worms). To get a free 60-days evaluation version of RAV AntiVirus v8 (yet fully functional) please visit: http://www.ravantivirus.com -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Re: Details [Virus Detected]
*** Content Management Alert Your message was not delivered. Royal SunAlliance's content management process detected a virus and quarantined the message. From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Details Date: Wed, 3 Sep 2003 7:21:02 --0400 [EMAIL PROTECTED] Please virus check and re-send your attachments. (Note: I/RSACM) *** -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync 2.5.6, No buffer space available error...
I have seen this error in many postings, but the solutions seem not to apply in this case. This error happens during a small file transfer (gif image) and after 75% of a 165G rsync job (the building file list portion is complete.) Most solutions I saw were related to not having enough RAM or running out of disk space. Check out the machine specs below the error. rsync: writefd_unbuffered failed to write 4830 bytes: phase unknown: No buffer space available rsync error: error in rsync protocol data stream (code 12) at io.c(515) rsync: writefd_unbuffered failed to write 69 bytes: phase unknown: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) uptime reports 11:17pm up 8:43, 2 users, load average: 1.65, 1.40, 1.33 IBM x330 server 2x1.4GHz PIII 4G RAM RedHat 7.2 (2.4.7-10smp -- required for veritas) rsync 2.5.6 local vxfs source and destination (different filesystems) and destination has 800G of free space (ideally the source will be on another machine, but I made it local to simplify troubleshooting... same problem with an NFS source) rsync command used: rsync -Wav --stats /sourcedir /destdir /opt/rsync.log 21 and syslog reports: Aug 31 04:07:57 moss kernel: ENOMEM in do_get_write_access, retrying. Aug 31 04:16:05 moss kernel: journal_write_metadata_buffer: ENOMEM at get_unused_buffer_head, trying again. anyone seen this? -- Matt Miller IT Infrastructure Team Duke University - Fuqua School of Business -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync 2.5.6, No buffer space available error...
On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote: I have seen this error in many postings, but the solutions seem not to apply in this case. This error happens during a small file transfer (gif image) and after 75% of a 165G rsync job (the building file list portion is complete.) Most solutions I saw were related to not having enough RAM or running out of disk space. Check out the machine specs below the error. rsync: writefd_unbuffered failed to write 4830 bytes: phase unknown: No buffer space available rsync error: error in rsync protocol data stream (code 12) at io.c(515) rsync: writefd_unbuffered failed to write 69 bytes: phase unknown: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) uptime reports 11:17pm up 8:43, 2 users, load average: 1.65, 1.40, 1.33 IBM x330 server 2x1.4GHz PIII 4G RAM RedHat 7.2 (2.4.7-10smp -- required for veritas) rsync 2.5.6 local vxfs source and destination (different filesystems) and destination has 800G of free space (ideally the source will be on another machine, but I made it local to simplify troubleshooting... same problem with an NFS source) rsync command used: rsync -Wav --stats /sourcedir /destdir /opt/rsync.log 21 and syslog reports: Aug 31 04:07:57 moss kernel: ENOMEM in do_get_write_access, retrying. Aug 31 04:16:05 moss kernel: journal_write_metadata_buffer: ENOMEM at get_unused_buffer_head, trying again. anyone seen this? Not an rsync problem. This is a kernel issue. You seem to be out of ZONE_DMA memory. I don't know whether you should be reporting this to RH or Veritas or IBM but when you do be sure to send them /proc/slabinfo from the moment of error. One thing you might try is booting with mem=900M Running with more than 900M n 1G memory on 2.4 kernels is problematic. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
