From owner-freebsd-stable@FreeBSD.ORG Fri Feb 12 19:34:50 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 3A185106566B; Fri, 12 Feb 2010 19:34:50 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id CC8B38FC15; Fri, 12 Feb 2010 19:34:49 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAG88dUuDaFvI/2dsb2JhbACbAXS/TYRYBIMT X-IronPort-AV: E=Sophos;i="4.49,462,1262581200"; d="scan'208";a="65424566" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 12 Feb 2010 14:34:49 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 07285940025; Fri, 12 Feb 2010 14:34:49 -0500 (EST) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJLWgfnY1+Aj; Fri, 12 Feb 2010 14:34:46 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id C9F7B9400FD; Fri, 12 Feb 2010 14:34:45 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o1CJkBm29568; Fri, 12 Feb 2010 14:46:11 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 12 Feb 2010 14:46:11 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Dmitry Marakasov In-Reply-To: <20100212190848.GF94665@hades.panopticon> Message-ID: References: <20100212180032.GC94665@hades.panopticon> <201002121820.o1CIKohU019226@lurza.secnetix.de> <20100212190848.GF94665@hades.panopticon> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Oliver Fromme 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 19:34:50 -0000 On Fri, 12 Feb 2010, Dmitry Marakasov wrote: > * Oliver Fromme (olli@lurza.secnetix.de) wrote: > >> I'm sorry for the confusion ... I do not think that it's >> the cause for your data corruption, in this particular >> case. I just mentioned the potential problems with "soft" >> mounts because it could cause additional problems for you. >> (And it's important to know anyhow.) > > Oh, then I really misunderstood. If the curruption implied is > like when you copy a file via NFS and the net goes down, and in > case of soft mount you have half of a file (read: corruption), while > with hard mount the copy process will finish when the net is back up, > that's definitely OK and expected. > The problem is that it can't distinguish between "slow network/server" and partitioned/failed network. In your case (one client) it may work out ok. (I can't remember how long it takes to timeout and give up for "soft".) For many clients talking to an NFS server, the NFS server's response time can degrade to the point where "soft" mounted clients start timing out and that can get ugly. rick