From owner-freebsd-fs@FreeBSD.ORG Sat Mar 3 11:36:52 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8279D106564A for ; Sat, 3 Mar 2012 11:36:52 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 05A738FC13 for ; Sat, 3 Mar 2012 11:36:51 +0000 (UTC) Received: by eaaf13 with SMTP id f13so891008eaa.13 for ; Sat, 03 Mar 2012 03:36:51 -0800 (PST) Received-SPF: pass (google.com: domain of c.kworr@gmail.com designates 10.14.39.145 as permitted sender) client-ip=10.14.39.145; Authentication-Results: mr.google.com; spf=pass (google.com: domain of c.kworr@gmail.com designates 10.14.39.145 as permitted sender) smtp.mail=c.kworr@gmail.com; dkim=pass header.i=c.kworr@gmail.com Received: from mr.google.com ([10.14.39.145]) by 10.14.39.145 with SMTP id d17mr6995658eeb.86.1330774611006 (num_hops = 1); Sat, 03 Mar 2012 03:36:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=APO+GrupiHapVuQu38oM/FcU7BhENry6sIoTUaoQb/g=; b=kX9caoK5yIBCwHcMw4MS+2Mf16O/CBpWNGMNZZGX5J4/zGMZUHlLkN5VWS+lDPN0ry yeSiFI1il/h29doALShPosy3zBZbEikyKy+bnxl5brAFGWiXBYkXdlsoz3CXR400FS2f CjeddNz8BA2jIUKVd3ZDjmJVBf36Ookbh2j3y/HJPwzbEsO6jE/7zyZpKg7SnizHkn1n 8jgWAqcrxOc8Tk1rKtzdVlQ7w3PDA6VUnGfirUwv6SiIoT2qJB6qy8yyNZl5XZc1c+C3 wngLsfQCgKZ8YkO8Xu/APbOYUtFZcR0RrtnFO/6sVoY0WdqF5pHKrvNaRQF8MB80Rvj+ ns6Q== Received: by 10.14.39.145 with SMTP id d17mr5359155eeb.86.1330774610897; Sat, 03 Mar 2012 03:36:50 -0800 (PST) Received: from green.tandem.local (73-193-200-46.pool.ukrtel.net. [46.200.193.73]) by mx.google.com with ESMTPS id u11sm32950873eeb.1.2012.03.03.03.36.49 (version=SSLv3 cipher=OTHER); Sat, 03 Mar 2012 03:36:50 -0800 (PST) Message-ID: <4F520250.7090402@gmail.com> Date: Sat, 03 Mar 2012 13:36:48 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120220 Firefox/10.0.2 SeaMonkey/2.7.2 MIME-Version: 1.0 To: krad References: <4F50DCD8.9080603@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: zfs fails to mount correctly during 8.2 -> 9.0 update 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: Sat, 03 Mar 2012 11:36:52 -0000 krad wrote: > I have generally found this stepped method of booting into the new kernel > with the old userland as a bad thing with zfs. Especially if there is a zfs > version bump in the new build. This is due the the user land zfs tools > being out of sync with the kernel. What I have found works much better is > to clone your zfs root file system, mount it somewhere, set DESTDIR to > there and install world and kernel. Then tweak the loader.conf on the > relevent fs and the pools bootfs property accordingly. Unmount the new > root fs and set the mountpoint the legacy, then reboot. If you get problems > with the new build just boot in with a live ios and reset the bootfs > property of the pool to the old value. I wish the last step could be done > from the loader prompt but as far as i can see you cant yet 8( I know, this is rather "works for me" way of updating. However zfs userland is mostly not used for booting from or mounting zfs so its generally safe if the minimal set of commands for activating zfs works. This minimal set consists of: zfs mount -a zfs share -a And as far as I recall kernel interface for those was never touched so the previous tools work with new kernel module. One can even run new version of tools without installing them to system by creating some catalog in tmp and copying libraries and tools from /usr/obj to this catalog. Actually as far as I recall only thing bootfs flag does is refusing some advanced features like adding separate log/cache device. The system boots fine regardless bootfs setting. So mounting another file system as a root can be accomplished by setting or changing vfs.root.mountfrom at loader prompt. -- Sphinx of black quartz judge my vow.