From owner-freebsd-fs@FreeBSD.ORG Mon Dec 31 00:52:20 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67711C35 for ; Mon, 31 Dec 2012 00:52:20 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by mx1.freebsd.org (Postfix) with ESMTP id EB71F8FC12 for ; Mon, 31 Dec 2012 00:52:19 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id hn17so9113032wib.12 for ; Sun, 30 Dec 2012 16:52:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0xv4xxOCzUwHc1EYH4ICMQEvbx4tKEaKB4kMzQD1Ojc=; b=YKPFaeFfys4Wlbb0tVs9GOdL7dpTGwLBmuExTc7S1FttwgPDWT4po+7Kfn7l1fg33y gKXygLsxQ3uMLvt21rdgyOB7fPxZaW6ZW4wMSAQjOpb+Wdl4/cWo3m6SgmfGMcHRx1DM HkC88r+oC47LEggRNt/GhZodaV4vAUH4FzX5l6aanG27hFYB+Tj7/zSVEmrYJYzuNbnO qRFGTCN+N6ty8KWkGlMOfF5F5sRSiGGlCvig9iDBn9HeVq28mltxIlmh5bKfcKAmTFAb 0/52fTRKL0e+5wqTfBsrirIasIOpw5AzYHj1MPgC4eRdoRIdy6x6sfPy+SNtb1ioctHV 1PgQ== MIME-Version: 1.0 Received: by 10.180.93.40 with SMTP id cr8mr61792312wib.15.1356915133446; Sun, 30 Dec 2012 16:52:13 -0800 (PST) Received: by 10.216.172.197 with HTTP; Sun, 30 Dec 2012 16:52:13 -0800 (PST) In-Reply-To: <973d506368c26dda4f618556b071e454@mail.lifanov.com> References: <973d506368c26dda4f618556b071e454@mail.lifanov.com> Date: Mon, 31 Dec 2012 02:52:13 +0200 Message-ID: Subject: Re: Zpool made of ZVOLs? From: Kimmo Paasiala To: Nikolai Lifanov Content-Type: text/plain; charset=UTF-8 Cc: freebsd-fs@freebsd.org 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, 31 Dec 2012 00:52:20 -0000 On Mon, Dec 31, 2012 at 1:25 AM, Nikolai Lifanov wrote: >> Is it possible and even recommended to create a zpool out of block >> devices that are actually ZVOLs? >> >> I'd like to have a separate zfs pool for poudriere because building >> ports with it disrupts the snapshotting on my main pool if the >> poudirere jails are created on it. At the same time I don't want to >> resort to using external disks to create a pool that is only used for >> a jail or two. >> >> Regards, >> >> -Kimmo >> > > I'm sure that this is not what you want. > I think you are trying to snapshot your root pool and volatility + size of > poudriere data makes this impractical. The first pool would still be the > provider of zvols for the second pool. > If you can't have pools backed by separated devices (i.e. rpool on separate > disks from tank), then you can always arrange the data that poudriere is > interfering with to be on a different dataset. > So, from tank/poudriere/... arrangement you can move to tank/ROOT/... and > tank/DATA/poudriere. > > - Nikolai Lifanov I solved this by a vnode backed md(4) disk. I know that I could also use little more fine grained snapshoting and backups. Mow I'm just creating recursive back ups for the whole pool and backing up everything using one zfs send, zfs receive operation.