From: Steve Dickson Subject: Re: [NFS] nfs_statfs: statfs error = 512 ? Date: Wed, 23 Jan 2008 15:37:38 -0500 Message-ID: <4797A592.4080903@RedHat.com> References: <479763EC.3090601@bnl.gov> <4797699C.2020100@RedHat.com> <47976B05.60408@bnl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: nfs@lists.sourceforge.net To: Sev Binello Return-path: Received: from neil.brown.name ([220.233.11.133]:43736 "EHLO neil.brown.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751764AbYAWUh5 (ORCPT ); Wed, 23 Jan 2008 15:37:57 -0500 Received: from brown by neil.brown.name with local (Exim 4.63) (envelope-from ) id 1JHmM6-000863-BQ for linux-nfs@vger.kernel.org; Thu, 24 Jan 2008 07:37:54 +1100 In-Reply-To: <47976B05.60408-IGkKxAqZmp0@public.gmane.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: Sev Binello wrote: > The problem doesn't seem to occur on WS3 clients, but does on WS4 > clients ? Again, I'm pretty sure this problem was identified and fixed in an later update release... you could try updating to the latest and greatest (U7). > Can you provide any more details ? An a bzip2 tethereal network trace something similar to tethereal -w /tmp/data.pcap host and host