Date: Mon, 8 May 2006 13:54:58 +0200 From: Yuri Khotyaintsev <yuri@irfu.se> To: freebsd-stable@freebsd.org Subject: NFS/TCP problems Message-ID: <200605081354.58807.yuri@irfu.se>
next in thread | raw e-mail | index | archive | help
I have an NSF server and several clients which write large text files to th= e=20 server. All machines are running max one week old STABLE and are connected = to=20 the same gigabit switch, and have identical nics (em). Amd mount options ar= e: /defaults =20 type:=3Dnfs;cache:=3Dall;opts:=3Drw,intr,nosuid,grpid,nfsv3,tcp,resvport,so= ft Almost all the time I get the following messages on the server: nfsd send error 32 nfsd send error 32 nfsd send error 32 nfsd send error 32 nfsd send error 32 =2E.. And corresponding messages on a client: impossible packet length (8996061) from nfs server db:/export/data1/caa impossible packet length (3123011) from nfs server db:/export/data1/caa impossible packet length (893006905) from nfs server db:/export/data1/caa impossible packet length (842018868) from nfs server db:/export/data1/caa impossible packet length (874220) from nfs server db:/export/data1/caa impossible packet length (14182767) from nfs server db:/export/data1/caa impossible packet length (16777216) from nfs server db:/export/data1/caa impossible packet length (758134573) from nfs server db:/export/data1/caa impossible packet length (1503661568) from nfs server db:/export/data1/caa impossible packet length (1300840) from nfs server db:/export/data1/caa =2E.. And from time to time the files which are written to the server get truncat= ed=20 (regardless of the file size)... Does anybody have an idea how to make it work reliably and not to truncate = the=20 files? =2D-=20 Dr. Yuri Khotyaintsev Institutet f=F6r rymdfysik (IRF), Uppsala
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605081354.58807.yuri>