From owner-freebsd-fs@FreeBSD.ORG Thu Nov 13 16:06:11 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99209943; Thu, 13 Nov 2014 16:06:11 +0000 (UTC) Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D3D7EFB; Thu, 13 Nov 2014 16:06:11 +0000 (UTC) Received: by mail-vc0-f174.google.com with SMTP id la4so3896516vcb.33 for ; Thu, 13 Nov 2014 08:06:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r89uvSsTXBS+47VOlI1U0OpjELiv/HPzJIIktcLuzP8=; b=gSL68YWoW+2AaGGJlLR+uisbyFQa4rBwvgLmuPgibc5MqOFIu4gzmd4Pyt7Uxw8xBt ba1omX4hPJRErc30vrA/qbwDWpOoj766z9vtxAxAhNHKz2ra0utG/gNgkq1JtR9J2iQQ tgBC2bIBXpz9YSJ/i4CvENnL/4bZ5/JUYFLlCXPvCxcJZK2/Q81E/UF9sU6/3E9PGuIH g+O1zCsls45eOka2vBehDlre1Lmtow4T2QtRhuWoGlOG7NoOHnrvCy7P3vsAepSLhCE3 OXFPnrlqU5ajMJSspmUH0/2aQPKJwCI3E3eY73lgJ3PMgXrVq20V4AgldFp2dwUhNBWX Njiw== MIME-Version: 1.0 X-Received: by 10.52.163.202 with SMTP id yk10mr1918796vdb.14.1415894770279; Thu, 13 Nov 2014 08:06:10 -0800 (PST) Received: by 10.31.142.2 with HTTP; Thu, 13 Nov 2014 08:06:10 -0800 (PST) In-Reply-To: <1415890567.2670730.190586365.02618860@webmail.messagingengine.com> References: <20141111080903.94302@smtp.new-ukraine.org> <5461BCB1.5030703@delphij.net> <20141111101004.845@smtp.new-ukraine.org> <1415715795.1681955.189655693.7993AEA6@webmail.messagingengine.com> <20141111223833.46741@smtp.new-ukraine.org> <1415890567.2670730.190586365.02618860@webmail.messagingengine.com> Date: Thu, 13 Nov 2014 18:06:10 +0200 Message-ID: Subject: Re: unsupported feature: com.delfix and can't find pool by guid after old STABLE10.0-to-RELENG10.0 upgrade From: Kimmo Paasiala To: Mark Felder Content-Type: text/plain; charset=UTF-8 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2014 16:06:11 -0000 Altroot does the right thing (tm) and moves all mountpoints to be relative to the altroot property, in other words the value of the altroot property is prepended to every mountpoint. Both inherited and explicitly set mountpoints behave exactly as you expect with altroot. -Kimmo On Thu, Nov 13, 2014 at 4:56 PM, Mark Felder wrote: > > > On Tue, Nov 11, 2014, at 14:38, Zeus Panchenko wrote: >> Mark Felder wrote: >> > All you should need to do is boot FreeBSD 10.1-RC4 and apply the newer >> > bootcode and put the newer kernel on the system. >> >> I hoped I could use my old kernel :( >> thanks, I'll try >> >> > >> > If this is a zfs-on-root install you may have problems with importing >> > the zpool and getting access to your data. I would advice you import the >> > zpool with the -N option >> > >> > -N Import the pool without mounting any file systems. >> >> emm ... why a not altroot ? >> >> zpool(8) >> >> altroot >> Alternate root directory. If set, this directory is prepended to >> any >> mount points within the pool. This can be used when examining an >> unknown pool where the mount points cannot be trusted, or in an >> alternate boot environment, where the typical paths are not >> valid. >> > > Altroot looks viable, but I haven't tested how it behaves. This my > question: > > > tank mountpoint=/ > tank/var mountpoint=/var (inherited) > tank/tmp mountpoint=/tmp (directly set) > > I expect altroot will correctly move the root (tank) and /var > (tank/var) to the altroot, but how does it handle other zfs filesystems > that have a very specific mountpoint set like /tmp in this situation? > Does it gracefully mount it into the mountroot, or does that only work > for the root and filesystems that inherit their mountpoint? > > As I have not tested it, I do not trust it. I'll certainly test this in > the near future, though. Thanks for the tip! > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"