From: Chuck Lever Subject: Re: Fwd: for your comments Date: Thu, 16 Feb 2006 09:09:00 -0500 Message-ID: <43F4877C.2020202@citi.umich.edu> References: <200602160435.k1G4ZWIJ148088@atlas.otago.ac.nz> Reply-To: cel@citi.umich.edu Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------010806070007020401050903" Cc: macosx-interop@lists.apple.com, nfs@lists.sourceforge.net, Cathy Chandra Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1F9jom-0004Po-Uo for nfs@lists.sourceforge.net; Thu, 16 Feb 2006 06:09:12 -0800 Received: from citi.umich.edu ([141.211.133.111]) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1F9jok-0001sT-Fd for nfs@lists.sourceforge.net; Thu, 16 Feb 2006 06:09:12 -0800 To: Dave Robertson In-Reply-To: Sender: nfs-admin@lists.sourceforge.net Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: This is a multi-part message in MIME format. --------------010806070007020401050903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dave Robertson wrote: > Hi, > > We'd like to report a problem we are seeing with NFS clients ( Fedora > Core 4 using kernel 2.6.15) served by OSX Server 10.4.4. > The clients randomly get an I/O error when attempting to list > the contents of the current directory, and we are also seeing "RPC: > error 5 connecting to server xxx.xxx.xxx.xxx" but > > "strace ls" shows the EIO is generated by the call to getdents64 as > shown below. > > No errors appear on the server. i know this is a sporadic error, but capturing a network trace while the error occurs would show why the client is having trouble connecting to the server. i use ethereal, but "tcpdump -s1536 -vv host yourserver" would also work. > The I/O error can be corrected by changing to another directory and > then listing the directory where the error occurred. usually this means that the client is able to reconnect properly to the server, and continue normal operation. > The network has been running well for two years prior to the upgrades. > Clients upgraded from FC3 to FC4 and the server from OSX 10.3.9 to 10.4.3. > > We are not seeing this on our other client OS (Tru-64) > We've also tried combinations of OSX Server 10.4.5 and FC5 Test 2 > (Linux 2.6.15) but the problem still surfaces. --------------010806070007020401050903 Content-Type: text/x-vcard; charset=utf-8; name="cel.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="cel.vcf" begin:vcard fn:Chuck Lever n:Lever;Charles org:Network Appliance, Incorporated;Open Source NFS Client Development adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA email;internet:cel@citi.umich.edu title:Member of Technical Staff tel;work:+1 734 763-4415 tel;fax:+1 734 763 4434 tel;home:+1 734 668-1089 x-mozilla-html:FALSE url:http://troy.citi.umich.edu/u/cel/ version:2.1 end:vcard --------------010806070007020401050903-- ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs