From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 04:30:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1E5916A420 for ; Tue, 5 Feb 2008 04:30:56 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from mindcrime.bit0.com (bit0.com [207.246.88.211]) by mx1.freebsd.org (Postfix) with ESMTP id 79F0013C442 for ; Tue, 5 Feb 2008 04:30:56 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from localhost (localhost [127.0.0.1]) by mindcrime.bit0.com (Postfix) with ESMTP id 37B311E33AE for ; Mon, 4 Feb 2008 23:30:55 -0500 (EST) X-Virus-Scanned: amavisd-new at bit0.com Received: from mindcrime.bit0.com ([127.0.0.1]) by localhost (mindcrime.int.bit0.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihfVP6fyG5fd for ; Mon, 4 Feb 2008 23:30:52 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mindcrime.bit0.com (Postfix) with ESMTP for ; Mon, 4 Feb 2008 23:30:52 -0500 (EST) Date: Mon, 4 Feb 2008 23:30:52 -0500 (EST) From: Mike Andrews X-X-Sender: mandrews@mindcrime.int.bit0.com To: freebsd-stable@freebsd.org Message-ID: <20080204230945.J49853@mindcrime.int.bit0.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: mount -p and NFS options X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 04:30:56 -0000 Is there anything like "mount -p" that will print the current NFS options in use? TCP vs UDP, v2 vs v3, read/write sizes etc. It doesn't have to be in fstab format; I just need to be able to see what the flags are for an active mount. This would be useful in tracking down an irritating NFS problem I've been experiencing with diskless systems in every 6.x release and 7.0-RC1, namely libc.so.6 appears to be truncated or corrupt to the client at somewhat random times... I think it may be related to mount options, hence the question. Mike Andrews * mandrews@bit0.com * http://www.bit0.com It's not news, it's Fark.com. Carpe cavy!