From owner-freebsd-fs@FreeBSD.ORG Wed Nov 25 00:28:05 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2111106568B for ; Wed, 25 Nov 2009 00:28:05 +0000 (UTC) (envelope-from mattjreimer@gmail.com) Received: from mail-pz0-f185.google.com (mail-pz0-f185.google.com [209.85.222.185]) by mx1.freebsd.org (Postfix) with ESMTP id BA1098FC16 for ; Wed, 25 Nov 2009 00:28:05 +0000 (UTC) Received: by pzk15 with SMTP id 15so4985037pzk.3 for ; Tue, 24 Nov 2009 16:28:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=+g4gVcr/PHcSBjl0LhGfq0+D9Naaar8YDnE4bqDqaNE=; b=djBH4DjFm9a9eNQyShn1VpLzZ2TP5eRi5RZyvSk9xr5163gcI3+30R5K9ZOMt2Higv 7nZkIc7sIP3tirl4HTLtRSdbCGMLdfQmnHap1Eo4xG0tBqKT49JQwjS0xBOuhM7TSldz 5NrzTDf1pg5n0KAprU6szyyaXpiGZilmd5kqc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wcTJW8UXYo6xMdm00BmEYan3vn6G7W81vBnvrTKmrGZd1aWbq25dy8VMVcqxA+UUof cosf3VQMgRQ21113x5RtxiHko9t/5gFF0wVdeqFwT/JMAzp2K22EXAGUot1I2U+xAnNm ik2N4UEbPCVCq0qRphdeABivgU87XQZz2eN08= MIME-Version: 1.0 Received: by 10.142.121.10 with SMTP id t10mr166720wfc.308.1259108885364; Tue, 24 Nov 2009 16:28:05 -0800 (PST) In-Reply-To: <4B0BC896.8030808@jrv.org> References: <4B0BC896.8030808@jrv.org> Date: Tue, 24 Nov 2009 16:28:05 -0800 Message-ID: From: Matt Reimer To: "James R. Van Artsdalen" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs Subject: Re: Current gptzfsboot limitations X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2009 00:28:06 -0000 On Tue, Nov 24, 2009 at 3:50 AM, James R. Van Artsdalen wrote: > I assume that *zfsboot requires that /boot and /boot/kernel be in the > boot filesystem and not filesystems of their own. > > A man page probably ought to say this or someone will be tempted to "zfs > create pool/boot/kernel" so they can roll back undesirable kernel installs. gptzfsboot (and I'm pretty sure zfsboot too) uses the first pool it finds. It opens the pool, gets the 'bootfs' property (i.e. the one set with "zpool set bootfs=tank/ROOT tank") and retrieves loader(8) from that filesystem. You can boot from any filesystem in the pool. Matt