From owner-freebsd-stable@FreeBSD.ORG Mon Feb 8 22:17:43 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 0BCD4106568F; Mon, 8 Feb 2010 22:17:43 +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 A188E8FC2B; Mon, 8 Feb 2010 22:17:42 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEALMbcEuDaFvJ/2dsb2JhbADXHIRUBA X-IronPort-AV: E=Sophos;i="4.49,432,1262581200"; d="scan'208";a="64833033" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 08 Feb 2010 17:17:41 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 9E7F8FB808C; Mon, 8 Feb 2010 17:17:41 -0500 (EST) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJOpihBQ2MjL; Mon, 8 Feb 2010 17:17:40 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id D5A97FB8039; Mon, 8 Feb 2010 17:17:40 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o18MSvt17944; Mon, 8 Feb 2010 17:28:57 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 8 Feb 2010 17:28:57 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "O. Hartmann" In-Reply-To: <4B704804.4030802@zedat.fu-berlin.de> Message-ID: References: <4B6FE550.9020506@zedat.fu-berlin.de> <4B704804.4030802@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 22:17:43 -0000 On Mon, 8 Feb 2010, O. Hartmann wrote: >> >> 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. >> > > Interesting, I see a lot of vfs.newfs-stuff on server-side, but not this > specific OID. Do I miss something here? > Oops, make that vfs.newnfs.enable_locallocks=0 rick