From owner-freebsd-stable@FreeBSD.ORG  Thu Mar 18 13:19:03 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@www.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 423E916A4CE
	for <freebsd-stable@www.freebsd.org>;
	Thu, 18 Mar 2004 13:19:03 -0800 (PST)
Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 39B7943D2D
	for <freebsd-stable@www.freebsd.org>;
	Thu, 18 Mar 2004 13:19:03 -0800 (PST)
	(envelope-from mandrews@bit0.com)
Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])
	by mx2.freebsd.org (Postfix) with ESMTP id 2E8C755507
	for <freebsd-stable@lists.freebsd.org>;
	Thu, 18 Mar 2004 13:19:03 -0800 (PST)
	(envelope-from mandrews@bit0.com)
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2BDE216A4CE
	for <freebsd-stable@lists.freebsd.org>;
	Thu, 18 Mar 2004 13:19:03 -0800 (PST)
Received: from bit0.com (bit0.com [216.24.42.194])
	by mx1.FreeBSD.org (Postfix) with SMTP id AEE6443D2D
	for <freebsd-stable@lists.freebsd.org>;
	Thu, 18 Mar 2004 13:19:02 -0800 (PST)
	(envelope-from mandrews@bit0.com)
Received: from localhost (localhost.bit0.com [127.0.0.1])
	by bit0.com (Postfix) with ESMTP
	id 2607D34D33; Thu, 18 Mar 2004 16:19:45 -0500 (EST)
Date: Thu, 18 Mar 2004 16:19:45 -0500 (EST)
From: Mike Andrews <mandrews@bit0.com>
To: Doug White <dwhite@gumbysoft.com>
In-Reply-To: <20040318123302.W63293@carver.gumbysoft.com>
Message-ID: <20040318161712.T4263@mindcrime.bit0.com>
References: <20040318144807.E95350@mindcrime.bit0.com>
 <20040318123302.W63293@carver.gumbysoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-stable@lists.freebsd.org
Subject: Re: Weird NFSvs rdirplus issues
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Mar 2004 21:19:03 -0000

> On Thu, 18 Mar 2004, Mike Andrews wrote:
>
> > I've been experimenting with readdirplus and running into two bizarre situations.
> >
> > Bizarre situation #1 is the easy one: when you try to put the acdirmin/max
> > and acregmin/max options on an NFS filesystem in /etc/fstab, mount
> > (actually mount_nfs) will dump core on 4.9-RELEASE-p4 but not on
> > 5.2.1-RELEASE-p3:
> >
> > # grep acreg /etc/fstab
> > server:/fs /mnt nfs,ro,-lis,acdirmin=0,acdirmax=1,acregmin=0,acregmax=1 0 0
> > # mount /mnt
> > mount: server:/fs: Segmentation fault
>
> What happens if you change "-lis" to "rdirplus,soft,intr,nfsv3"?
> Readdirplus is a v3 call so it might imply it anyway, but best to be safe.

Same thing.  It's definitely using v3.  The default is to try 3 then back
down to 2, but I did try explicitly forcing 3 and it made no difference.

Though that does bring up another point: it would be nice if 'mount' (with
no arguments) would tell you what your currently active options are, like
it does for ufs.  I did find some discussion of this in the archives, but
no definitive indication that it was planned (and it's not in 5.2.1...)


Mike Andrews  *  mandrews@bit0.com  *  http://www.bit0.com
"The truth is, you never find the truth."     Carpe cavy!
It's not news, it's Fark.com.