From owner-freebsd-fs@FreeBSD.ORG Sun May 21 16:36:55 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26EDF16A41F for ; Sun, 21 May 2006 16:36:55 +0000 (UTC) (envelope-from amdmi3@mail.ru) Received: from mx7.mail.ru (mx7.mail.ru [194.67.23.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADD4743D4C for ; Sun, 21 May 2006 16:36:54 +0000 (GMT) (envelope-from amdmi3@mail.ru) Received: from [213.148.29.33] (port=14083 helo=nexii.panopticon) by mx7.mail.ru with esmtp id 1FhqvF-000KQL-00; Sun, 21 May 2006 20:36:53 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.2]) by nexii.panopticon (Postfix) with ESMTP id 3079C11449; Sun, 21 May 2006 20:41:27 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 544FCA00; Sun, 21 May 2006 20:38:03 +0400 (MSD) Date: Sun, 21 May 2006 20:38:03 +0400 From: Dmitry Marakasov To: Scott Long Message-ID: <20060521163803.GB923@hades.panopticon> Mail-Followup-To: Scott Long , freebsd-fs@freebsd.org References: <20060521132527.GA67386@hades.panopticon> <44708B42.9050608@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <44708B42.9050608@samsco.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org Subject: Re: NFS safety in 6.1-RELEASE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 16:36:55 -0000 * Scott Long (scottl@samsco.org) wrote: > >So I wanted to ask what's status of NFS for release - was that issue > >fixed and is it safe to use client and server NFS on 6.1 RELEASE? > >If there's still data corruption possible, how do I turn off the > >attribute cache? > > Dang, I meant to document that before the release, sorry. There are two > variants > that I've seen with 6.1. One is between a Linux client and a FreeBSD > server. This > seems to be effectively fixed by using a 2.6.12 or later Linux kernel. My cases are 6.0 server - 6.1 client and 6.1 - 6.1 > The other is > due to any client or server disagreeing on the precision of the > timestamps that are > passed in the attributes. This disagreement can lead to the attribue > cache getting > confused and returning incorrect data to the caller. It can be turned > off by either > changing the default timeouts to 0 that are defined in the nfsclient > code, or by setting > the appropriate mount options in mount_nfs as per the man page. Thanks a lot for the help. Do I get it right that only file attributes may be currupted, not the data itself? -- Best regards, Dmitry mailto:amdmi3@mail.ru