From owner-freebsd-stable@FreeBSD.ORG Fri Feb 12 17:54:26 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79256106566B; Fri, 12 Feb 2010 17:54:26 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [92.53.116.15]) by mx1.freebsd.org (Postfix) with ESMTP id 2AFCA8FC16; Fri, 12 Feb 2010 17:54:25 +0000 (UTC) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1NfziU-0002TW-4q; Fri, 12 Feb 2010 20:54:10 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id E0ABBB860; Fri, 12 Feb 2010 20:54:22 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id C9D4BB829; Fri, 12 Feb 2010 20:54:22 +0300 (MSK) Date: Fri, 12 Feb 2010 20:54:22 +0300 From: Dmitry Marakasov To: Rick Macklem Message-ID: <20100212175422.GB94665@hades.panopticon> References: <20100210174338.GC39752@hades.panopticon> <201002111255.46256.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, John Baldwin Subject: Re: NFS write corruption on 8.0-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2010 17:54:26 -0000 * Rick Macklem (rmacklem@uoguelph.ca) wrote: > > Is it the hostname of the server or the client? > > My guess is that hades.panopticon (or something like that:-) is the Yes, that is the client. > As John said, it would be nice to try and narrow it down to client or > server side, too. I'm planning a massive testing for this weekend, including removing soft mount option and trying linux client/server. Btw, I forgot to mention that I'm experiencing other NFS problems from time to time, including "death" of a mount (that is, all processes that try to access it freeze; this cures itself in some time with a message "server is alive again"). Also I've seen another strange thing - not only the mount dies but the network is flooded with NFS traffic. Last time I've seen it quite a while ago, so I don't remember the circumstances and direction of the traffic. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru