From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 19:50:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 523661065670 for ; Sun, 25 Jan 2009 19:50:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from aeryn.cs.uoguelph.ca (aeryn.cs.uoguelph.ca [131.104.20.160]) by mx1.freebsd.org (Postfix) with ESMTP id 87A878FC12 for ; Sun, 25 Jan 2009 19:50:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by aeryn.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id n0Q0MqDQ001244; Sun, 25 Jan 2009 19:22:52 -0500 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n0PJQAi17277; Sun, 25 Jan 2009 14:26:11 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Sun, 25 Jan 2009 14:26:10 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Dmitry Marakasov In-Reply-To: <20090123221826.GB30982@deprived.panopticon> Message-ID: References: <20090123221826.GB30982@deprived.panopticon> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.20.161 Cc: freebsd-current@freebsd.org Subject: Re: NFS data corruption X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2009 19:50:03 -0000 On Sat, 24 Jan 2009, Dmitry Marakasov wrote: [stuff about data corruption snipped] > > Is there any way I can help to diagnose and fix the problem? > > Here's amd.map file which is used to mount this filesystem: > > --- > /defaults type:=nfs;rhost:=hive;opts:=rw,nosuid,noexec,-3,-i,-s,-T > * rfs:=/pool/${key} > --- > A couple of simple things you could try: 1 - rebuild your kernel with "option NFS_LEGACYRPC" and try that. 2 - try it without the "-s" option (since nothing reports a failure, is seems unlikely that an RPC would have timed out, but maybe the app. doesn't check for error returns on write. In general, I consider "soft" mounts to be a bad idea, but that's just imho.) Good luck with it, rick