From owner-freebsd-stable@FreeBSD.ORG Mon Feb 8 17:19:38 2010 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 97144106566C; Mon, 8 Feb 2010 17:19:38 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 50E2C8FC0C; Mon, 8 Feb 2010 17:19:38 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1NeXGr-000830-CX>; Mon, 08 Feb 2010 18:19:37 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1NeXGr-0004aT-At>; Mon, 08 Feb 2010 18:19:37 +0100 Message-ID: <4B704804.4030802@zedat.fu-berlin.de> Date: Mon, 08 Feb 2010 17:21:08 +0000 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100206 Thunderbird/3.0.1 MIME-Version: 1.0 To: Rick Macklem References: <4B6FE550.9020506@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: NFSv4: mount -t nsf4 not the same as mount_newnfs? 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: Mon, 08 Feb 2010 17:19:38 -0000 On 02/08/10 15:08, Rick Macklem wrote: > > > On Mon, 8 Feb 2010, O. Hartmann wrote: > >> >> Mounting the filessystem via >> >> mount_newnfs host:/path /path >> > Oh, and you should set: > sysctl vfs.newnfs.locallocks_enable=0 > in the server, since I haven't fixed the local locking yet. (This implies > that apps/daemons running locally on the server won't see byte range > locks performed by NFSv4 clients.) However, byte range locking between > NFSv4 clients should work ok. > > rick > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Interesting, I see a lot of vfs.newfs-stuff on server-side, but not this specific OID. Do I miss something here? Regards, Oliver