From owner-freebsd-current  Fri Oct 29  8:23:15 1999
Delivered-To: freebsd-current@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 7DED11503A
	for <freebsd-current@FreeBSD.ORG>; Fri, 29 Oct 1999 08:22:57 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA23320;
	Fri, 29 Oct 1999 11:22:53 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA34322;
	Fri, 29 Oct 1999 11:22:22 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Oct 1999 11:22:22 -0400 (EDT)
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: odd NFS behaviour with DU 4.F client
In-Reply-To: <199910282225.PAA12530@apollo.backplane.com>
References: <14360.50663.727201.679421@grasshopper.cs.duke.edu>
	<199910282225.PAA12530@apollo.backplane.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14361.47885.374557.603037@grasshopper.cs.duke.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Matthew Dillon writes:
 > 
 >     Well, there was a bug in nfsrv_create() which caused the server to
 >     not reply to an NFS packet.  This led to a general revamping of the
 >     server side code which may have fixed other rpc's at the same time.
 >     Whether fixing that bug solves the problem you are having or not is 
 >     unknown.
 > 
 > :I would guess that the DU4CLIENT has the filehandle cached somewhere,
 > :even though it has unmounted the filesystem.  
 > :
 > :My question: Whose fault is this?  Should the FreeBSD server be
 > :ignoring requests to a valid filehandle if the client has not mounted
 > :the FS?  Should it be returning some sort of error?
 > :
 > :Thanks,
 > :
 > :Drew
 >  
 >     There should be a response to the rpc either way so my guess is that
 >     it is a server-side bug.

It turns out that the user was in 17 groups (DU supports up to 32).
After I removed him from 2 groups & got his group count down to 15,
all was well.

After I upgrade the NFS server to a more recent -current, I'll test
this again with a user in 17 groups.

Thanks again,

Drew



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message