SFTP delivers mangled files if over 40 mb


I've tested multiple files from zip to tar to rar and other compressed files. If the file is over 40 mb, and it's uploaded or downloaded, it's mangled on the target server. This is using scp or sftp. The bytes match exactly, however their's crc and format errors in the compressed files.


guideX wrote Sep 12, 2008 at 4:00 AM

This is found to be a problem with VMWare ESX ONLY

guideX wrote Apr 22, 2009 at 4:39 AM

Someone on codeproject said if you change the variables dealing with file size into long's instead of ints, you can transfer big files where otherwise would corrupt them. Haven't tried it yet, but I'm going to now.

guideX wrote May 2, 2009 at 6:15 PM

I tried it, but i'm too unfamiliar with this huge project to make the appropriate changes, could you do it?

wrote Nov 5, 2009 at 10:00 PM

icnocop wrote Nov 5, 2009 at 10:02 PM

I am also experiencing this issue when trying to upload a ~500mb iso file to VMWare ESX

icnocop wrote Nov 5, 2009 at 10:58 PM

SFTP Server Version: SSH-2.0-OpenSSH_3.6.1p2
SFTP Client Version: SSH-2.0-SharpSSH-

icnocop wrote Nov 6, 2009 at 10:48 AM

Here are some notes for source code improvements to make this project more manageable:
  1. remove java\String.cs and replace it with System.String
  2. remove java\System.cs and replace it with Array.Copy, Console.WriteLine, and Console.Error.WriteLine where applicable
  3. remove java\Exception.cs and replace it with System.Exception
  4. remove old code (Channel.old.cs) and commented code
  5. improve JStream, PipedInputStream, PassiveInputStream, InputStreamGet, InputStream, FileInputStream, OutputStream, etc. by reusing already existing classes like BinaryReader, BinaryWriter, FileStream, StreamReader, StreamWriter, NetworkStream, etc.
  6. fix compile time warnings
  7. better exception handling (verbosely display\output exceptions)

icnocop wrote Nov 6, 2009 at 10:50 AM

  1. Find and remove casts like "(int)" and "(long)"

wrote Feb 14, 2013 at 12:17 AM