Date: Sun, 21 May 2006 20:38:03 +0400 From: Dmitry Marakasov <amdmi3@mail.ru> To: Scott Long <scottl@samsco.org> Cc: freebsd-fs@freebsd.org Subject: Re: NFS safety in 6.1-RELEASE Message-ID: <20060521163803.GB923@hades.panopticon> In-Reply-To: <44708B42.9050608@samsco.org> References: <20060521132527.GA67386@hades.panopticon> <44708B42.9050608@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060521163803.GB923>