Hi, I'm getting the following error when dding a big file on an nfs mount which is mounted using TCP. root_at_kartoffel olivleh1> dd if=/usr/tmp.data of=/mnt/files/tmp.data bs=32k dd: /mnt/files/tmp.data: Resource temporarily unavailable 639+0 records in 638+0 records out 20905984 bytes transferred in 15.066490 secs (1387582 bytes/sec) Exit 1 root_at_dill olivleh1> dd if=/usr/tmp.data of=/mnt/files/tmp.data bs=32k dd: /mnt/files/tmp.data: Resource temporarily unavailable 1035+0 records in 1034+0 records out 33882112 bytes transferred in 14.698220 secs (2305185 bytes/sec) Exit 1 dmesg gives me "nfs send error 35 for server file:/mnt/files" fstab entry on kartoffel and dill: file:/mnt/files /mnt/files nfs tcp,nfsv3,soft,bg,rw,noauto 0 0 - kartoffel is an amd64 system with an onboard re0 running CURRENT from May 24th evening. - dill is an alpha system with an xl0 running 5.4 STABLE from May 20th - file is an i386 SMP system with an xl0 running 5.4 STABLE from May 20th - dill and file are connected directly through an switch - kartoffel and file are connected through an router+switches. - kartoffel and nudel are running rpc.lockd and rpc.statd - dill doesn't run rpc.lockd neither rpc.statd Switching from nfsv3 to a nfsv2 mount is much slower and breaks sooner or later with an error too. It doesn't give me an "error 35" on client side, but an "nfsd send error 32" on server side and a slightly different error message: root_at_kartoffel olivleh1> dd if=/usr/tmp.data of=/mnt/files/tmp.data bs=32k dd: /mnt/files/tmp.data: Operation timed out 67+0 records in 66+0 records out 2162688 bytes transferred in 6.221855 secs (347595 bytes/sec) Exit 1 Switching from TCP to UDP makes this error gone. Any ideas how to fix this properly? (please CC me, I'm not subscribed to stable_at_) -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/Received on Wed May 25 2005 - 16:46:41 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:35 UTC