Corrupting Files with SFTP on Linux

[terrychamilton]

When I send a number of files over SFTP some of the
files will end up getting their names mixed up.

For example:

Queue up 10 files IMAGE001.gif to IMAGE010.gif

001 is 1kb
002 is 2kb
...
010 is 10kb

After the batch is done the receiver has the files as:

001 is 2kb (001 is really 002 but mis-named)
002 is 1kb (it's really 001)
003 ok
...
009 is 10kb (it's really 010)
010 is 9kb (it's really 009)

It happens to any files, binary or text (GIF, PHP,
HTML, PDF, etc.). So far there has been no actual
corruption of the files, just the switching of filenames.

Randomly positioned in the upload order, not always the
first or last files.

The files switched are always sequencial in the list of
files (alphabetical) and it always happens in pairs.

It seems pretty random. Sometimes it will be 50% or
more of the files other times it will be 2 out of 30.

Uploading/Downloading from Windows to Redhat SFTP.
Happens across multiple hosts (and hosting services).

It happens both ways, getting and sending files.

Not related to the file names as simply re-sending the
files works. Next attempt will likely be different
files in the list.

[Tim Kosse]

Are you using any routers? Almost all users experiencing
problems with swapped filenames were using Linksys routers
so far.

[terrychamilton]

Yes. Linksys WRT54G firmware 4.20.7.

So far I haven't detected any file corruption other than the
random name swapping.

[marguskohv]

Happened to me too when downloading MULTIPLE FILES ! Files
are not corrupt, it just swaps filenames. If downloading
files one by one everything is okay. I am using FZ 2.2.27.

[marguskohv]

Oh, and I have LinkSys router too... what should something
like that have anything to do with router ?

[marguskohv]

Sorry for so many posts, but I think I've solved this issue
temporarily. By enabling "Active Transfer Mode" all files
were downloaded correctly. Hopefully this helps someone :)

[Alexander Schuch]

So the problem with a Linksys router has been worked around?
If not, simply re-open this bug report.