From owner-freebsd-current@FreeBSD.ORG Wed Jan 25 22:44:49 2012 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 D337A106564A for ; Wed, 25 Jan 2012 22:44:49 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 608808FC12 for ; Wed, 25 Jan 2012 22:44:48 +0000 (UTC) Received: by bkbc12 with SMTP id c12so6532532bkb.13 for ; Wed, 25 Jan 2012 14:44:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8eJwYWswOcoOxgubQfXSDOH3pJtEeeZAH1yo8ohs2IQ=; b=yBEHKwVhjgrxHibUbFDu2j5mX3PZfAbkCW/xYk78FqBK0bGdK9oOE9PmStijQwGbLQ 42lUyS0mvAqvT86EcSBNgNw3PhpIAIDs2wTGd6WaKDnwLpS4Xxf9dkCVvLw9ZsXqYy0k IF5d3rIWw3sYflZPRkjpcDE4WAo1ielgB89xM= MIME-Version: 1.0 Received: by 10.205.129.20 with SMTP id hg20mr8028691bkc.77.1327531488135; Wed, 25 Jan 2012 14:44:48 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.204.179.15 with HTTP; Wed, 25 Jan 2012 14:44:48 -0800 (PST) In-Reply-To: <666472979.73336.1327451522107.JavaMail.root@erie.cs.uoguelph.ca> References: <666472979.73336.1327451522107.JavaMail.root@erie.cs.uoguelph.ca> Date: Wed, 25 Jan 2012 14:44:48 -0800 X-Google-Sender-Auth: AEAa6BbVe4Q4hAuUFCN0-wXlUeI Message-ID: From: Craig Rodrigues To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: Heads Up: NFS clients can now fail "mount -u -o udp..." 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: Wed, 25 Jan 2012 22:44:49 -0000 On Tue, Jan 24, 2012 at 4:32 PM, Rick Macklem wrote: > > As such, specifying "udp" or "mntudp" options in the /etc/fstab > entry for "/" on a diskless NFS client could result in the "mount -u" > failing. I'd suggest that "udp" and "mntudp" be avoided for this > case, if you are using the default of TCP for the root mnt done > when the diskless client is booted. If a user boots with an NFS root mount, and does not specify UDP or TCP, what is the default transport protocol used? If I user does: "mount -t nfs ...." or "mount_nfs ...." from the command-line, and does not specify UDP or TCP, what is the default transport protocol used? I would like to see the default become TCP in both cases. It would solve a lot of "FreeBSD out of the box" problems when interacting with more modern NFS servers. -- Craig Rodrigues rodrigc@crodrigues.org