From owner-freebsd-fs@FreeBSD.ORG Thu Sep 12 19:24:22 2013 Return-Path: Delivered-To: freebsd-fs@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 ESMTP id 37AA7F36 for ; Thu, 12 Sep 2013 19:24:22 +0000 (UTC) (envelope-from lkchen@k-state.edu) Received: from ksu-out.merit.edu (ksu-out.merit.edu [207.75.117.133]) by mx1.freebsd.org (Postfix) with ESMTP id 00A492F52 for ; Thu, 12 Sep 2013 19:24:21 +0000 (UTC) X-Merit-ExtLoop1: 1 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFACgUMlLPS3TT/2dsb2JhbABbgweBCoMqvlYWdIIlAQEFI1YMDxoCDRkCWQaIFah7iS2ITYEpkTKBNAOiLoc+gz6CDg X-IronPort-AV: E=Sophos;i="4.90,892,1371096000"; d="scan'208";a="78051035" X-MERIT-SOURCE: KSU Received: from ksu-sfpop-mailstore02.merit.edu ([207.75.116.211]) by sfpop-ironport03.merit.edu with ESMTP; 12 Sep 2013 15:23:01 -0400 Date: Thu, 12 Sep 2013 15:23:00 -0400 (EDT) From: "Lawrence K. Chen, P.Eng." To: Mark Martinec Message-ID: <99471506.80369991.1379013780610.JavaMail.root@k-state.edu> In-Reply-To: <201309091956.53759.Mark.Martinec+freebsd@ijs.si> Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [129.130.0.181] X-Mailer: Zimbra 7.2.2_GA_2852 (ZimbraWebClient - GC29 ([unknown])/7.2.2_GA_2852) 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, 12 Sep 2013 19:24:22 -0000 ----- Original Message ----- > Adam Nowacki writes: > > zfs set mountpoint=legacy data/root > > together with > > zpool set bootfs=data/root data > > > > setting vfs.root.mountfrom is not required - this is handled by the > > bootfs property, as is listing / in fstab > > So what happens if multiple pools each have their bootfs set? > > Mark > _______________________________________________ Unless things have changed...the boot loader only looks at the first freebsd-zfs partition on the disk its booting. Tripped me up once because originally I had a swap partition before my root zpool, but switched to in pool swap so I thought I would just turn the swap partition into an extra zpool. Had hoped using zfs would fix the random disk errors in swap bringing me down, ended up keeping it swap but gmirror'd. Later found I had a bad DIMM and a flaky controller.... Lawrence