From owner-freebsd-current@FreeBSD.ORG Fri Sep 11 20:32:39 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8444F1065672 for ; Fri, 11 Sep 2009 20:32:39 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 239298FC1C for ; Fri, 11 Sep 2009 20:32:38 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEABdRqkqDaFvI/2dsb2JhbADdWoQYBYFU X-IronPort-AV: E=Sophos;i="4.44,372,1249272000"; d="scan'208";a="45973473" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 11 Sep 2009 16:32:38 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 18D5E9400A6; Fri, 11 Sep 2009 16:32:38 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VeLkRbP3-ion; Fri, 11 Sep 2009 16:32:36 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id D1936940078; Fri, 11 Sep 2009 16:32:36 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8BKboE10143; Fri, 11 Sep 2009 16:37:51 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 11 Sep 2009 16:37:50 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Doug Poland In-Reply-To: Message-ID: References: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, FreeBSD Current Subject: RE: NFS issues on 8.0-BETA4 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: Fri, 11 Sep 2009 20:32:39 -0000 >> >> I cannot sucessfully mount exports from the NFSv3 server on the >> 8.0-BETA4 client. All works well with 7.2 clients. >> >> The strange thing is, the directory in which I mount the nfs >> filesystem disappears, and I get an error when I attempt to access the >> directory. >> I went and looked at the message over in stable@ (I guess I have to join that mailing list, too:-). I think that the second mount attempt, which failed with errno==64 EHOSTDOWN probably gives you a better indication of what is broken and hints at a networking problem, which hopefully others can help with? mount_nfs currently has the quirk that, if you don't specify either "udp" or "tcp", it will use UDP for the mount protocol and then switch to TCP for NFS. (I didn't make it that way, but noticed it when I was adding changes for the experimental client.) So, you might want to try adding "udp" or "tcp" to the mount options for your "simplified mount" and see what happens? (I suggest this, since it seems to have been able to talk to mountd on the server, but not NFS on the server and the only explanation I can think of is the switch to TCP for that.) I think the first case failed after the retrycnt, due to the "soft" option, but hadn't succeeded in doing any NFS Getattr, so the mount point's type wasn't VDIR--> returning errno==1 EPERM for the "ls -l". If the mount attempts with "udp" or "tcp" specified give you the same behaviour, you could try using wireshark to capture the traffic. (Wireshark is pretty good at decoding NFS traffic.) If you don't have wireshark, you can use "tcpdump -w -s 0 " to capture the traffic in a file that can be fed to wireshark later. (I'd be happy to look at the traffic, if you were to email me the above .) Good luck with it, rick ps: I'll assume that the client can talk to the server for other stuff ok. pss: A big change between 7 and 8 is use of a new kernel RPC layer that handles the RPC transport (again, I wasn't the author, but am somewhat familiar with it).