Date: Thu, 1 Jul 2010 11:01:04 -0700 (PDT) From: alan bryan <alan.bryan@yahoo.com> To: freebsd-stable@freebsd.org Subject: NFS 75 second stall Message-ID: <425902.41392.qm@web50501.mail.re2.yahoo.com>
next in thread | raw e-mail | index | archive | help
Setup:=0A=0Aserver - FreeBSD 8-stable from today.=A0 2 UFS dirs exported vi= a NFS.=0Aclient - FreeBSD 8.0-Release. Running a test php script that copi= es around various files to/from 2 separate NFS mounts.=0A=0ASituation: =0A= =0Ascript is started (forked to do 20 simultaneous runs) and 20 1GB files a= re copied to the NFS dir which works fine.=A0 When it then switches to read= ing those files back and simultaneously writing to the other NFS mount I se= e a hang of 75 seconds.=A0 If I do an "ls -l" on the NFS mount it hangs too= .=A0 After 75 seconds the client has reported:=0A=0Anfs server 192.168.10.1= 33:/usr/local/export1: not responding=0Anfs server 192.168.10.133:/usr/loca= l/export1: is alive again=0Anfs server 192.168.10.133:/usr/local/export1: n= ot responding=0Anfs server 192.168.10.133:/usr/local/export1: is alive agai= n =0A=0Aand then things start working again.=A0 The server was originally F= reeBSD 8.0-Release also but was upgraded to the latest stable to see if thi= s issue could be avoided.=0A=0A# nfsstat -s -W -w 1=0A GtAttr Lookup Rdlink= =A0=A0=A0Read=A0 Write Rename Access=A0 Rddir=0A=A0 =A0 =A0 0=A0 =A0 =A0 0= =A0 =A0 =A0 0=A0 =A0 222=A0 =A0 257=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 178=A0 =A0 135=A0 =A0 =A0= 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 = =A0=A0=A085=A0 =A0 127=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0= 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0= =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 = =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0= 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 = =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =0A=0A... for 75 rows of all zeros=0A=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 272=A0 =A0 266=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 = =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 167=A0 =A0 165=A0 =A0 =A0 0=A0 = =A0 =A0 0=A0 =A0 =A0 0=0A=0AI also tried runs with 15 simultaneous processe= s and 25. 15 processes gave only about a 5 second stall but 25 gave again = the same 75 second stall. =0A=0AFurther, I tested with 2 mounts to the sa= me server but from ZFS filesytems with the exact same stall/timeout periods= . So, it doesn't appear to matter what the underlying filesystem is - it's= something in NFS or networking code.=0A=0AAny ideas on what's going on her= e? What's causing the complete stall period of zero NFS activity? Any fl= aws with my testing methods?=0A=0AThanks for any and all help/ideas.=0A=0A-= -Alan=0A=0A=0A=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?425902.41392.qm>