Date: Wed, 27 Oct 2004 10:22:10 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Ben Mesander <ben@timing.com> Cc: current@freebsd.org Subject: Re: -current NFSv2 and NFSv3 issues Message-ID: <20041027172210.GA59514@xor.obsecurity.org> In-Reply-To: <16767.52483.986921.670394@piglet.timing.com> References: <16767.52483.986921.670394@piglet.timing.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 27, 2004 at 10:29:55AM -0600, Ben Mesander wrote: > Hi all, >=20 > We're seeing some data corruption and performance problems here with > NFSv3/TCP on a machine running -current NFS client against a 4.8 NFS > server. >=20 > The problems can be reproduced by doing a 'make buildworld' over > NFS. With NFSv2 & UDP we could buildworld with -j8 and the build > would usually - but not always - complete successfully. The times when > it did not appeared to possibly be a result of the mtime.tv_usec not > being checked for files over NFS (ie, one build step creates a .depend > file, and another step tries to use it before it "appears" over NFS). Is this a vfs.nfs.access_cache_timeout issue? I don't remember if that does negative caching as well. Kris --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBf9lCWry0BWjoQKURAv5pAJwOgfEal3fIAuDVp5OIC10J9T0nMQCg6hWk 8UM7NN2h+Dd4aduE5ehiwHg= =4LCn -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041027172210.GA59514>