From owner-freebsd-questions@FreeBSD.ORG Fri Aug 8 15:30:22 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6929F6BF for ; Fri, 8 Aug 2014 15:30:22 +0000 (UTC) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) (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 2749421E0 for ; Fri, 8 Aug 2014 15:30:21 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id i13so5514244qae.20 for ; Fri, 08 Aug 2014 08:30:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=9zfXaQn7UmxHEUr/bWxrj/bj05MuEZkOjMA3jYkyUFE=; b=VWj7CdC7PqnGe9Jklr83xNXGpOky4mY8YMe5yWVWX2QG8GVAAR+jSdCbyHmDWZgNDm HcviKMIF8oPTFLdRB+y1gYvjlCjaTR4MlLZB8SL59qqwke1TnGVrImjc8a4UBxR+XBYB 4mwLb/imuZ6IHtLpRJ3+nFm2ITRx5QvgBcGvc/Z/DJYLfcdjC/vMu88vwjeoAbFW3eD7 SezTyCPIhOX+h6NyQsNhWYoqhGrWCxqWk4T3mrTnUf9NleWxsu3S2q57J2e139fRxyf4 1iWKiQZycuc0OCQDtnXyp3L80DBu/1AOEuMH7VENihxA5qa0TkUbIlt5bP+W/YmMb52j hEFg== X-Gm-Message-State: ALoCoQlSC7vdc5ELsufoXC0WKKtD2noSk05wM4JISDcsPZkhG8dG5qn6g+0tWjX/lqDlx6PhaiVL X-Received: by 10.224.156.194 with SMTP id y2mr19256444qaw.15.1407511820484; Fri, 08 Aug 2014 08:30:20 -0700 (PDT) Received: from [192.168.1.127] (c-71-234-255-65.hsd1.vt.comcast.net. [71.234.255.65]) by mx.google.com with ESMTPSA id w11sm6028160qax.30.2014.08.08.08.30.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Aug 2014 08:30:19 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: some ZFS questions From: Paul Kraus In-Reply-To: <201408070816.s778G9ug015988@sdf.org> Date: Fri, 8 Aug 2014 11:30:18 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <27DAA821-0303-4D51-ADA7-7780DB8FE85D@kraus-haus.org> References: <201408070816.s778G9ug015988@sdf.org> To: Scott Bennett , FreeBSD Questions !!!! X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 15:30:22 -0000 On Aug 7, 2014, at 4:16, Scott Bennett wrote: > One thing I ran across was the following from the zpool(8) man = page. >=20 > "For pools to be portable, you must give the zpool command whole > disks, not just slices, so that ZFS can label the disks with portable > EFI labels. Otherwise, disk drivers on platforms of different endian- > ness will not recognize the disks.=94 Here is where understanding *why* helps you make better decisions. In = order for a zpool to be importable (is that even a word?) on a given = system, the underlying OS must be able to read the parse the partition = information. Since the *only* partition system that *all* the OSes that = support ZFS understand is EFI, you need to use that if you want to have = a truly portable zpool. I *think* you can manually create the EFI and = just put zpools in the various partitions, but I am not positive. If you only care about moving zpools between FreeBSD systems, and KNOW = that you will NEVER want to import this pool on, for example, a Solaris = system, then you can use any partition system FreeBSD understands. I = have used GPT and moved zpools around between FreeBSD systems without a = problem. The critical part is that the OS must understand the partitioning and be = able to present to the ZFS kernel module the data from within the = partitions. Each partition that contains a zpool top level vdev will = include 4 copies of the ZFS header, 2 at the start of the device and 2 = at the end (note that I am saying device here, that could be an entire = disk or a partition or even a file acting as a block device). So, if the = ZFS code can read all 4 labels from the device, it can import this vdev, = if it can import a sufficient number of vdevs that make up a zpool, it = can import the zpool. > If I have one raidzN comprising .eli partitions and another raidzN = comprising > a set of unencrypted partitions on those same drives, will I be able = to > export both raidzN pools from a 9-STABLE system and then import them > into, say, a 10-STABLE system on a different Intel amd64 machine? I am not familiar with FreeBSD .eli partitions, I assume at some layer = below the block device the OS is encrypting the data here. If that is a = valid assumption, then I=92ll take a stab at answering :-) If the OS can = read the data from the device and find the ZFS labels it can import that = vdev (and with enough vdevs it can import the zpool). > By your > answer to question 1), it would seem that I need to have two raidzN = pools, > although there might be a number of benefits to having both encrypted = and > unencrypted file systems allocated inside a single pool were that an = option. Oracle has done work on ZFS to permit native encryption within ZFS. I do = not know off the top of my head if that is on a zpool or dataset basis. = I expect that it is probably on a dataset basis, so you could have both = encrypted and unencrypted datasets within one zpool (just as we can have = both compressed and uncompressed datasets). -- Paul Kraus paul@kraus-haus.org