From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 11:02:17 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 957911065674; Thu, 13 Nov 2008 11:02:17 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from itchy.rabson.org (unknown [IPv6:2002:50b1:e8f2:1::143]) by mx1.freebsd.org (Postfix) with ESMTP id 50A0B8FC16; Thu, 13 Nov 2008 11:02:17 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from [IPv6:2001:470:909f:1:21b:63ff:feb8:5abc] (unknown [IPv6:2001:470:909f:1:21b:63ff:feb8:5abc]) by itchy.rabson.org (Postfix) with ESMTP id 40D693FAD; Thu, 13 Nov 2008 11:01:33 +0000 (GMT) Message-Id: <3BFE7716-48E7-4AE9-BE82-611FBA57C837@rabson.org> From: Doug Rabson To: Navdeep Parhar In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Thu, 13 Nov 2008 11:02:15 +0000 References: <440834F1-1CA0-424F-915F-3B3CD773F83B@rabson.org> X-Mailer: Apple Mail (2.929.2) Cc: dfr@freebsd.org, freebsd-current@freebsd.org Subject: Re: problems with nfsd (due to RPCSEC_GSS changes?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 11:02:17 -0000 On 12 Nov 2008, at 19:36, Navdeep Parhar wrote: > On Wed, Nov 12, 2008 at 1:20 AM, Doug Rabson wrote: >> >> On 12 Nov 2008, at 01:30, Navdeep Parhar wrote: >> >>> I had a FreeBSD NFS server running a month+ old current (from Oct >>> 2 or >>> so). I upgraded to a current current (Nov 11) and nfsd stopped >>> working. >>> I was able to mount the exported filesystem but anything else would >>> yield an "Input/output error." nfsstat -s showed "Server Ret-Failed" >>> going up everytime I tried a 'cd', 'ls', etc. from the client. (I >>> tried >>> both FreeBSD and Solaris clients). >>> >>> Ultimately, I had to add NFS_LEGACYRPC in order to get a working >>> nfsd. >>> Looks like there may be a problem with the new code that was added >>> as >>> part of RPCSEC_GSS support. Note that I did not enable KGSSAPI in >>> my >>> kernel as I have no need for it. >>> >>> Are there any knows issues with the new code? Feel free to ask if >>> you >>> need any more information about my setup. >> >> I don't know of anything specific. If I could see a packet trace >> including >> both the mount request and at least one failed access attempt, it >> would help >> to understand what is happening here. >> > > I saw a handful of commits from you last night so I updated + > rebuilt the > server's kernel to include them. These traces are with today's code > (Nov12 > 11AM Pacific) on the server and yesterday's code on the client. > > The server is .2 and the client is .1, the trace is using tcpdump -s > 256 -vvn on the server. > > # mount /usr/obj (and then wait a couple of seconds. The mount > succeeds) Could you try this again with 'tcpdump -w foo.pcap ...' and then send me the resulting file - its very hard to see what is really happening from a simple tcpdump output.