From owner-freebsd-stable@FreeBSD.ORG Tue Jun 2 22:32:51 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEE5E1065673 for ; Tue, 2 Jun 2009 22:32:51 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id 717AA8FC1C for ; Tue, 2 Jun 2009 22:32:51 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id DA98071F212; Tue, 2 Jun 2009 18:32:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eC43wnFcyLXK; Tue, 2 Jun 2009 18:32:50 -0400 (EDT) Received: from [35.9.44.65] (daemon.egr.msu.edu [35.9.44.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mx.egr.msu.edu (Postfix) with ESMTPSA id B6C9271F1D8; Tue, 2 Jun 2009 18:32:50 -0400 (EDT) Message-ID: <4A25A892.80903@egr.msu.edu> Date: Tue, 02 Jun 2009 18:32:50 -0400 From: Adam McDougall User-Agent: Thunderbird 2.0.0.21 (X11/20090419) MIME-Version: 1.0 To: Dan Naumov References: <8B50CE3F-FCC5-42D6-8FFE-591178F3DFB6@ish.com.au> <5f67a8c40906021147h48bc1c36y5de42fdc0d18677e@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Zaphod Beeblebrox , freebsd-stable@freebsd.org Subject: Re: ZFS NAS configuration question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 22:32:52 -0000 I have a proof of concept system doing this. I started with a 7.2 install on zfs root, compiled world and kernel from 8, took a snapshot and made a clone for the 7.2 install, and proceeded to upgrade the current fs to 8.0. After updating the loader.conf in the 7.2 zfs to point to its own cloned fs, I can pick which one to boot with a simple "zpool set bootfs=z/ROOT/7.2" or "zpool set bootfs=z/ROOT/8.0" before rebooting. I also tried rsyncing from a FFS based system into a new ZFS in that same zpool, used DESTDIR with installkernel and installworld to update the imported OS to support zfs, setup its boot loader and misc config files, and was able to boot from it using zpool to set it as the bootfs. Somewhat like shifting around OS images in a virtualization environment except its easy to reach inside the "image" to upgrade/modify it, copy them between systems, and no execution overhead while running one since its still on bare metal (but only one running OS per server of course). This makes it very easy to swap an OS onto another server if you need better/lesser hardware or just want to test. Dan Naumov wrote: > This reminds me. I was reading the release and upgrade notes of OpenSolaris > 2009.6 and noted one thing about upgrading from a previous version to the > new one:: > > When you pick the "upgrade OS" option in the OpenSolaris installer, it will > check if you are using a ZFS root partition and if you do, it intelligently > suggests to take a current snapshot of the root filesystem. After you finish > the upgrade and do a reboot, the boot menu offers you the option of booting > the new upgraded version of the OS or alternatively _booting from the > snapshot taken by the upgrade installation procedure_. > > Reading that made me pause for a second and made me go "WOW", this is how > UNIX system upgrades should be done. Any hope of us lowly users ever seeing > something like this implemented in FreeBSD? :) > > - Dan Naumov > > > > > > On Tue, Jun 2, 2009 at 9:47 PM, Zaphod Beeblebrox wrote: > > >> The system boots from a pair of drives in a gmirror. Mot because you can't >> boot from ZFS, but because it's just so darn stable (and it predates the use >> of ZFS). >> >> Really there are two camps here --- booting from ZFS is the use of ZFS as >> the machine's own filesystem. This is one goal of ZFS that is somewhat >> imperfect on FreeBSD at the momment. ZFS file servers are another goal >> where booting from ZFS is not really required and only marginally >> beneficial. >> >> >> >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >