Comment 16 for bug 661294

I tried to reproduce this as simply as possible:

Server: Lucid (2.6.32-26) , nfs-kernel-server (1.2.0-4ubuntu4), nfs-common (1.2.0-4ubuntu4)
- AMD based
- exported fs ext4, exported like in comment #10 (rw,sync)
Client: Maverick (2.6.35-23), nfs-common (1.2.2-1ubuntu1)
- Intel based
- target fs ext4

Connection is 1000Mbit/full duplex according to ethtool. I did the mount without any special options, just a plain "mount <ip>:/...". One thing I noticed is that

192.168.2.5:/srv/share/nfs /mnt nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.2.5,mountvers=3,mountport=37472,mountproto=udp,addr=192.168.2.5 0 0

my wsize and rsize values are smaller. And I use ext4 instead of ext3. But that should hopefully be not the issue. Anyway, something seems different because I successfully copy a 4GB file without issues. So we likely need to find out exactly what the failing setup is.

Has anybody running into this tried to run the actual copy from vt1 (that usually gets the console errors and may show something that does not make it into the logs)?