From owner-freebsd-current Wed Jan 28 14:59:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12821 for current-outgoing; Wed, 28 Jan 1998 14:59:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12814 for ; Wed, 28 Jan 1998 14:59:13 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id PAA09280; Wed, 28 Jan 1998 15:56:32 -0700 (MST) Date: Wed, 28 Jan 1998 15:56:32 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801282256.PAA09280@narnia.plutotech.com> To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: Another observation on -current and NFS Newsgroups: pluto.freebsd.current In-Reply-To: <199801280852.TAA29752@godzilla.zeta.org.au> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk In article <199801280852.TAA29752@godzilla.zeta.org.au> you wrote: >> Well, FWIW, I'll share my experiences with -current's NFS today. I >>have noticed the 'strip' problem happening as well for the past couple of >>months at least. In my experience, the client machine (i.e. the one doing >>the strip) wouldn't hang, but the kernel it generated wouldn't boot. > > Strip on the client often gave different file contents than strip on the > server. > >> There is one interesting NFS problem I can report, though. >>Apparantly there is a problem with access(2) and files on NFS mounted >>filesystems. (one of my co-workers discovered it) > > This look like the nfsv3 bug fixed (?) in PR5148. nfsv2 doesn't have it. > > Bruce Are we waiting on someone to review this patch? We can test it out here at Pluto, but I don't pretend to know anything about our NFS code. -- Justin