From owner-freebsd-stable Wed May 15 11: 2:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mighty.grot.org (mighty.grot.org [204.182.56.120]) by hub.freebsd.org (Postfix) with ESMTP id 299D537BB6C for ; Wed, 15 May 2002 11:01:39 -0700 (PDT) Received: by mighty.grot.org (Postfix, from userid 515) id B0AF95E7E; Wed, 15 May 2002 11:01:33 -0700 (PDT) Date: Wed, 15 May 2002 11:01:33 -0700 From: Aditya To: Peter Jeremy Cc: freebsd-stable@freebsd.org Subject: Re: Problems using 4.6-PR as an NFS server Message-ID: <20020515180133.GA41961@mighty.grot.org> Reply-To: Aditya References: <20020515122905.J18023@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020515122905.J18023@gsmx07.alcatel.com.au> X-PGP-Key: http://www.grot.org/pubkey.asc X-PGP-Key-ID: 0x6405D8D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a tangential suggestion, but do you have the same problem if you use a v3/TCP mount? Adi On Wed, May 15, 2002 at 12:29:05PM +1000, Peter Jeremy wrote: > I have a machine running 4.6-PRERELEASE #0: Wed May 8 03:17:26 EST 2002 > that is acting as an NFS server to a DEC/Compaq/HP Tru64 box. My problem > is that when the client user has is a member of too many groups, any NFS > requests are ignored by the server. > > As an example, I belong to 26 groups on the client and if I attempt to > do a "df", the following packet is just repeated forever with no > response from the server: > > 12:04:33.152440 aald02-tu0.244945956 > aalp03-a0.nfs: 220 fsstat fh 973,721824/2 > 0x0000 4500 00f8 c8ee 0000 1d11 3985 8bbc 270c E.........9...'. > 0x0010 8bbc 5bfd 03f7 0801 00e4 afb2 0e99 9424 ..[............$ > 0x0020 0000 0000 0000 0002 0001 86a3 0000 0003 ................ > 0x0030 0000 0012 0000 0001 0000 0094 3ce1 c231 ............<..1 > 0x0040 0000 0015 6161 6c64 3032 2e61 6c63 6174 ....aald02.alcat > 0x0050 656c 2e63 6f6d 2e61 7500 0000 0000 00cc el.com.au....... > 0x0060 0000 0064 0000 001a 0000 0064 0000 0000 ...d.......d.... > 0x0070 0000 001f 0000 0065 0000 0068 0000 00c8 .......e...h.... > 0x0080 0000 0190 0000 01f4 0000 01f5 0000 0069 ...............i > 0x0090 0000 00ce 0000 01f9 0000 006b 0000 01f8 ...........k.... > 0x00a0 0000 ea62 0000 0013 0000 006d 0000 001a ...b.......m.... > 0x00b0 0000 0067 0000 006a 0000 006c 0000 01f6 ...g...j...l.... > 0x00c0 0000 00ca 0000 01fb 0000 0063 0000 00c9 ...........c.... > 0x00d0 0000 0000 0000 0000 0000 001c a003 db3c ...............< > 0x00e0 8c48 9c49 0c00 0000 0200 0000 f02a 3b4b .H.I.........*;K > 0x00f0 0000 0000 0000 0000 ........ > > I thought that NFS behaviour in this case was to just take the first > 16 groups and ignore the remaining ones. I'm not enough of an NFS > expert to know if this is a problem on the client or server (and I > can't read RPC packets by hand). > > This is an NFSv3/UDP mount with an exports line of > /mnt -alldirs -maproot=root aald02 aald03 > > Any suggestions on where to look for a solution? > > Peter > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message