From owner-freebsd-fs@FreeBSD.ORG Thu Jul 4 15:54:14 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DD443106 for ; Thu, 4 Jul 2013 15:54:14 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 33D311E0F for ; Thu, 4 Jul 2013 15:54:13 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA12717; Thu, 04 Jul 2013 18:53:50 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Uulqv-000Evg-NZ; Thu, 04 Jul 2013 18:53:49 +0300 Message-ID: <51D59A55.1050807@FreeBSD.org> Date: Thu, 04 Jul 2013 18:52:53 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: Dmitry Morozovsky Subject: Re: boot from ZFS: which pool types use? References: <51D56066.1020902@FreeBSD.org> <51D56C19.8080103@FreeBSD.org> <51D57305.2010709@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Thu, 04 Jul 2013 15:54:14 -0000 on 04/07/2013 18:50 Dmitry Morozovsky said the following: > On Thu, 4 Jul 2013, Andriy Gapon wrote: > >> on 04/07/2013 15:43 Dmitry Morozovsky said the following: >>> it was/is (and, as I previously stated, is the only ZFS dataset on the >>> machine), but unfortunately without explicit setting bootfs property does not >>> work :( >> >> This is some confusing wording. We talk about _pools_ on a machine and we talk >> about _datasets_ in a pool. So I am not 100% sure what you mean. Whether you >> have a single pool, or whether you have a single dataset/filesystem in a pool, >> or both. >> >> Hint: output of commands is usually better than a bunch of free-form text :) > > Ah, I see the point, and the root dataset of the pool is *not* the root in my > case: > > root@briareus:/usr/src# zfs list > NAME USED AVAIL REFER MOUNTPOINT > br 13.3G 1.05T 31K legacy > br/R 13.3G 1.05T 389M / > br/R/db 8.30G 1.05T 8.30G /db > br/R/usr 4.51G 1.05T 3.44G /usr > br/R/usr/local 363M 1.05T 363M /usr/local > br/R/usr/ports 416M 1.05T 302M /usr/ports > br/R/usr/ports/distfiles 113M 1.05T 113M /usr/ports/distfiles > br/R/usr/src 317M 1.05T 317M /usr/src > br/R/var 122M 1.05T 122M /var > root@briareus:/usr/src# zpool get bootfs > NAME PROPERTY VALUE SOURCE > br bootfs br/R local > > /R is to have single mountpoint and possibility to have other root datasets to > use as non-mounted (iSCSI volumes, etc) > Right. So in this case it is purely a pilot error. ZFS can not know that among the available datasets br/R is the root fs. Thus bootfs must be set. -- Andriy Gapon