From owner-freebsd-fs@FreeBSD.ORG Sun Jan 17 20:43:51 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31A911065670 for ; Sun, 17 Jan 2010 20:43:51 +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 DEF118FC12 for ; Sun, 17 Jan 2010 20:43:50 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEACUFU0uDaFvK/2dsb2JhbADTcYQyBA X-IronPort-AV: E=Sophos;i="4.49,292,1262581200"; d="scan'208";a="61770910" Received: from fraser.cs.uoguelph.ca ([131.104.91.202]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 17 Jan 2010 15:43:50 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 17E7A109C2C6; Sun, 17 Jan 2010 15:43:50 -0500 (EST) X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca Received: from fraser.cs.uoguelph.ca ([127.0.0.1]) by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5NfkQwLjAdU; Sun, 17 Jan 2010 15:43:49 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 9DE97109C2C2; Sun, 17 Jan 2010 15:43:49 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o0HKsCF01815; Sun, 17 Jan 2010 15:54:12 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Sun, 17 Jan 2010 15:54:12 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Zane C.B." In-Reply-To: <20100116235857.6f126ad0@vixen42.vulpes> Message-ID: References: <20100116235857.6f126ad0@vixen42.vulpes> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org Subject: Re: odd NFS issues X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jan 2010 20:43:51 -0000 On Sat, 16 Jan 2010, Zane C.B. wrote: > Regardless of if I am mounting a NFS export remotely or locally, I > get the error below if I do a ls or any thing. > > Any suggestions? > > Below is a example of what happens if I try it locally. > > # mount_nfs -o mntudp,ro 192.168.15.2:/arc /mnt/ Oh, and it's just a stab in the dark, but I think that "ro" is handled by the generic mount command and that might be confusing it so that it doesn't recognize "mntudp" and is trying to use TCP. (which became the default somewhere along the way) You might try: mount -t nfs -o mntudp,ro ... instead? rick