From owner-freebsd-fs@FreeBSD.ORG Mon Sep 2 15:54:31 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F22964C2 for ; Mon, 2 Sep 2013 15:54:30 +0000 (UTC) (envelope-from ericbrowning@skaggscatholiccenter.org) Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA6CE2CE8 for ; Mon, 2 Sep 2013 15:54:30 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id rq2so4919700pbb.33 for ; Mon, 02 Sep 2013 08:54:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=CvjmeKUDlQwLMDZD7EBmOXqWf85bZcHXlzO4Sl5EfLs=; b=AdqxJAYY3g4ctH+EpsjvkAMtoTrr86xE4QD7fB+g13/OCnv77s9xiaA9l275KdLr+/ aIbnFIcx1NwCg/ZT7BtsuyA9br5vCHRxrgmwU2Rzb6BN0gy7g1IpgEhb7NJGvTkKhJuK lmvAqvayCM2rlhvJGrHuARgF2daLLlGXPQf05x6LVQgXqhuTQCclNlEw/o8FNrKCC+1K 1ymsti5uzgP4nJYZ+NvYbyL5z5JtJdKCWzqhE+4fDQSQrn+9m745lTPUFDGQEaMhI3uB ROUKjQos1LvKUMjxgY69V7JYD4oRgTjeWAX7UqzHqzID1/+FYJtreRrFefpR/ZHJfX4K gZJw== X-Gm-Message-State: ALoCoQnPXNFOHcrVJ8506Jsh4q0lBfXxzHUy5o+b3Z0vnD+UGAORi9wruLhQJAhAFY8Wi1BlDzF2 MIME-Version: 1.0 X-Received: by 10.68.137.170 with SMTP id qj10mr26265772pbb.31.1378136925752; Mon, 02 Sep 2013 08:48:45 -0700 (PDT) Received: by 10.70.26.4 with HTTP; Mon, 2 Sep 2013 08:48:45 -0700 (PDT) In-Reply-To: <590302855.16994708.1378131018328.JavaMail.root@uoguelph.ca> References: <590302855.16994708.1378131018328.JavaMail.root@uoguelph.ca> Date: Mon, 2 Sep 2013 09:48:45 -0600 Message-ID: Subject: Re: NFS on ZFS pure SSD pool From: Eric Browning To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2013 15:54:31 -0000 Rick, Thanks for the suggestions. mapping of names/uid is working correctly, on my own files I can see my uid on my files. Because of my mix of clients 10.6/7/8 I'm using just nfs v3 until those 10.6 clients die out. I'd like to eventually switch to nfsv4. I can't jail off the nfsv3 10.6 clients via MAC address since many of them overlap with the 10.7 clients which are just one model newer. nfs.client.access_cache_timeout is now set to 600 seconds instead of 60 nfs.client.access_for_getattr by default is off and of the three versions of OSX (10.6/7/8) Sam and I can experiment with sys/fs/nfs/nfs_commonsubs.c after we see if the mac client tweaks work this week. It's currently labor day and the school is closed. On Mon, Sep 2, 2013 at 8:10 AM, Rick Macklem wrote: > Sam Fourman Jr. wrote: > [lots of stuff snipped for brevity] > > root@students:/users # nfsstat -e -s > > > > Server Info: > > Getattr Setattr Lookup Readlink Read Write Create > > Remove > > 106273793 1417764 19593633 12021 2497674 7927757 1047249 > > 772450 > > Rename Link Symlink Mkdir Rmdir Readdir RdirPlus > > Access > > 319284 924 13813 63500 20980 526257 0 > > 677005862 > I didn't spot this when it first was posted, because of the wrap around. > > That's a *lot* of Access operations, imho. Maybe tweaking the Mac OS X > client > could reduce these? > > I see there are a couple of options in their nfs.conf(5) file that might > help? > nfs.client.access_cache_timeout > nfs.client.access_for_getattr > > You could also look at their mount_nfs man page to see if there are other > settings for access related stuff. > > As well, I'm wondering if the Macs may be doing Access ops like crazy > because > they see that ACLs are enabled. > I think ZFS always have ACLs enabled, but you can change the line in > sys/fs/nfs/nfs_commonsubs.c > int nfsrv_useacl = 1; > to > int nfsrv_useacl = 0; > and then build/boot a new kernel on the server to disable them. (It isn't > a sysctl, because it normally depends on the server file system to say if > they are supported.) > > Also, pull up a terminal window and do an "ls -l" on some directory, to > make > sure everything isn;t owned by "nobody". If it is, the name/uid mapping for > NFSv4 isn;t working correctly. > > Good luck with it, rick > > -- Eric Browning Systems Administrator 801-984-7623 Skaggs Catholic Center Juan Diego Catholic High School Saint John the Baptist Middle Saint John the Baptist Elementary