From owner-freebsd-questions@FreeBSD.ORG Fri Aug 8 11:54:46 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 A0F349F2 for ; Fri, 8 Aug 2014 11:54:46 +0000 (UTC) Received: from sdf.lonestar.org (mx.sdf.org [192.94.73.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "SDF.ORG" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8065E2751 for ; Fri, 8 Aug 2014 11:54:45 +0000 (UTC) Received: from sdf.org (IDENT:bennett@sdf.lonestar.org [192.94.73.15]) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s78BrYbc019909 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Fri, 8 Aug 2014 11:53:34 GMT Received: (from bennett@localhost) by sdf.org (8.14.8/8.12.8/Submit) id s78BrXoX011819; Fri, 8 Aug 2014 06:53:33 -0500 (CDT) From: Scott Bennett Message-Id: <201408081153.s78BrXoX011819@sdf.org> Date: Fri, 08 Aug 2014 06:53:33 -0500 To: Trond Endrest?l , freebsd-questions@freebsd.org Subject: Re: freebsd-questions Digest, Vol 531, Issue 6 References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 11:54:46 -0000 On Thu, 7 Aug 2014 10:33:09 +0200 (CEST) Trond Endrest?l wrote: >On Thu, 7 Aug 2014 03:16-0500, Scott Bennett wrote: >> On Wed, 6 Aug 2014 03:49:37 -0500 Andrew Berg >> wrote: >> >On 2014.08.06 02:32, Scott Bennett wrote: >> >> >> >> [much deleted --SB] >> >> >> >> 2) How does one start or stop a pool? >> >That depends on what you mean by 'start' and 'stop'. I am guessing by what you >> >described that you mean 'import' and 'export'. I'm not sure how to prevent >> >> Oh. Okay. At least there is some way to accomplish the same thing. >> >> >automatic import for pools that were imported on the same system and not >> >exported prior to shutdown, but I am sure it can be done. Resilvering does not >> >> Maybe someone else will say how it can be done. >> >> >mercilessly thrash disks; standard reads and writes are given higher priority >> >in the scheduler than resilver and scrub operations. >> >> If two pools use different partitions on a drive and both pools are >> rebuilding those partitions at the same time, then how could ZFS *not* >> be hammering the drive? > >Why would you place multiple pools on the very same drives? Because I need about 1/4 of my usable data space on those drives to be encrypted and the other 3/4 to be unencrypted, I need (according to another respondent) to build my raidzN pool from .eli components and the rest from unencrypted components. > >The only real world example I can think of is having separately >mirrored boot and root pools using the same drives. See above. > >E.g., bootpool using ada0p2 and ada1p2 as its mirrors, and rootpool >using adap0p3 and ada1p3 as its mirrors, with ada0p1 and ada1p1 being >the gpt boot partitions, and possibly with swap partitions on ada0p4 >and ada1p4. > Those low-space-requiring uses are also good examples of why a multiterabyte drive might need to be divided into different partitions with only some of them dedicated to ZFS. I had hoped to put some small partitions in between the large ones for other uses, too. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************