Date: Mon, 30 Apr 2012 22:45:58 -0500 From: "James R. Van Artsdalen" <james-freebsd-fs2@jrv.org> To: Peter Jeremy <peterjeremy@acm.org> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS with multiple boot/root pools Message-ID: <4F9F5C76.3030106@jrv.org> In-Reply-To: <20120501003937.GB53691@server.vk2pj.dyndns.org> References: <20120430210711.GA50280@server.vk2pj.dyndns.org> <4F9F0EC6.1060802@shatow.net> <20120501003937.GB53691@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/30/2012 7:39 PM, Peter Jeremy wrote: > That's OK for preventing filesystems on the secondary boot pool from > auto-mounting when booting from the primary pool but doesn't handle > booting from the secondary pool - a "zfs mount -a" there will > automount all the primary filesystems instead of the wanted secondary > ones. Don't do "zfs mount -a" from the secondary pool. Put "zfs_enable=NO" in /etc/rc.conf there, set each filesystem in the second pool to mountpoint=legacy, and list each secondary filesystem in /etc/fstab in the secondary pool. When booting the secondary pool no filesystems are automounted so the main pool is not a problem in that environment. When booting the main pool no filesystem from the secondary pool is automounted since all of those have mountpoint=legacy. I always use /boot from the secondary pool and select environments by setting 'vfs.root.mountfrom="zfs:POOL/ROOTFS"' in /boot/loader.conf on the secondary pool. That's OK since the secondary pool easily rebuilt if necessary and it solves the problem of booting my main pool. The main pool is many disks in RAIDZ vdevs and the BIOS cannot address them all for booting. But the secondary pool is a single MIRROR vdev and one dev in that vdev is on the hosts' standard SATA connector and can always be entirely read via INT 13h.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F9F5C76.3030106>