Comment 8 for bug 71212

Figured I'd continue testing and now it's getting interesting!

As with the last tests, I'm using fairly large (over 2GB) files and copying to normal NFS mounts.

There are three machines involved here. Rainbird (my box, Edgy, 2.6.19), Swan (husband, Edgy, 2.6.19), and Stork (our server, Breezy, 2.6.17).

As already mentioned, if I tell Rainbird to push a file to Stork, it hangs and the transfer rate is slow. Cancelling the copy is very difficult, taking several second to a minute.

The same thing happens if I tell Rainbird to push a file to Swan, or if I tell Swan to push to Stork. Something interesting here however - watching Swan's network meter (wmnet) during those periods when Rainbird is hung, I can see that there is still data transfer - more in fact than when Rainbird is responding normally.

HOWEVER, if I log into Stork and instruct it to pull from Rainbird, it works fine - no hangs. The transfer averages 8.7 MB/sec and stays fairly smooth. The same thing happens if I instruct Swan to pull a file from Rainbird - no problems whatsoever.

So basically, it doesn't seem to matter which two machines are involved, as long as the data is being *pulled* from from the source machine to the destination machiner, rather than pushed from the source as would be the norm.