From owner-freebsd-questions@FreeBSD.ORG Thu Aug 21 14:32:24 2014 Return-Path: Delivered-To: freebsd-questions@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 ESMTPS id 62D90CAF for ; Thu, 21 Aug 2014 14:32:24 +0000 (UTC) Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1DF023D2D for ; Thu, 21 Aug 2014 14:32:23 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id x13so9234303qcv.26 for ; Thu, 21 Aug 2014 07:32:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=GmgYDClIEfuVzabtWQIYMqU+S0xtbIaJphFo6tSFz1U=; b=hP6Lw0Cuh5m88QCvWjlL0bqKYMPzKwYQR+gDWRO9FoxtLBz/nNMQAjEhlQ3mbbOkWo kxNaafo7oulB/ZTJmAAWvV2RI3ZLH/D6nVy6G16kPcCv/9rIM4AcDB6E00ULhP8+W77Y BNkuYHZjgNsuLYcAlHkjvZmT+VIUTq5sIyko2xvNZaKnfFV4pKkUvS3mc/6bIkE6claN k13nT3464M4GBzQQ/NHtK+6ZDO+TMdy+9ZyEXmK6Xh9SbTnY2760Njy06T8WGLDLicX5 hyjXROOI37BV/3pHAwCLCVtoSq89eHd21CHmC+9Guykan9UtNClqs7VosCaok1APfHTa FMKg== X-Gm-Message-State: ALoCoQmW2COVxYAKnOxYG+T093iaNKScLZVMjb+alOF1pobhSOEb+AxmVWLBfP83gMaXuTz2h8bx X-Received: by 10.140.30.66 with SMTP id c60mr25510899qgc.30.1408631176840; Thu, 21 Aug 2014 07:26:16 -0700 (PDT) Received: from [192.168.2.65] ([96.236.21.80]) by mx.google.com with ESMTPSA id b15sm46753853qac.36.2014.08.21.07.26.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 07:26:16 -0700 (PDT) Subject: Re: some ZFS questions Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=us-ascii From: Paul Kraus In-Reply-To: <201408211033.s7LAXWbN006985@sdf.org> Date: Thu, 21 Aug 2014 10:26:15 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201408070816.s778G9ug015988@sdf.org> <53E3A836.9080904@my.hennepintech.edu> <201408080706.s78765xs022311@sdf.org> <201408211033.s7LAXWbN006985@sdf.org> To: Scott Bennett X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 14:32:24 -0000 On Aug 21, 2014, at 6:33, Scott Bennett wrote: > Paul Kraus wrote: >> How much does the geli encryption cost in terms of space and speed? = Is there a strong reason to not encrypt ALL the data? It can be in = different zfs datasets (the ZFS term for a filesystem). In fact, I am = NOT a fan of using the base dataset that is created with every zpool; I = always create addition zfs datasets below the root of the zpool. >=20 > Copying a file from one .eli partition to another can easily run = up > to 25% on each of two cores of a Q6600. > I didn't realize that there would be a "base data set"; I thought = that > one had to create at least one file system or zvol in a pool in order = to > use the space at all. When you create a zpool you get both the zpool and a zfs dataset of the = same name. You can use this dataset, but if I am going to be creating = *any* other datasets in this zpool I do not. I only use hierarchical = datasets in very specific ways as there are rules on inheritance and = mount points. For example: zpool create a gets you a mounted on /a zfs create a/b then gets you a mounted on /a=20 a/b mounted on /a/b You can then set the mount point to anything you wish, but unless you = explicitly set it on a/b, b will always be mounted just under a. I do the following: zpool create m m mounted on /m zfs set mountpoint=3Dnone m m not mounted zfs create m/n=20 m not mounted m/n not mounted zfs set mounptpoint=3D/foo m/n m not mounted m/n mounted on /foo >>> How does one set a limit? Is there an undocumented sysctl = variable >>> for it? >>=20 >> $ sysctl -a | grep vfs.zfs >>=20 >> to find all the zfs handles (not all may be tunable) >=20 > Are they all documented somewhere? I have not found documentation for them, but I also have not looked = through the source code. I am an admin and not a developer, so looking = through the source would be of limited use for me. I expect that many of = them map to the similar kernel parameters under Illumos (Solaris) and = most of those that you might want to change are documented (but I do not = recall where right now). -- Paul Kraus paul@kraus-haus.org