From owner-freebsd-current@freebsd.org Thu Mar 10 15:38:54 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C70EACA1D7; Thu, 10 Mar 2016 15:38:54 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 574053E0; Thu, 10 Mar 2016 15:38:54 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qg0-x231.google.com with SMTP id u110so73436369qge.3; Thu, 10 Mar 2016 07:38:54 -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; bh=lgVWkPrWP1XWoPa+dj0908s7trRWSBUtAulmXbbAkzU=; b=A+cdOf7Jy57No0ZKMCYhBsybsMM+7oLEEXHel6QaetiY35q0k3HQmWA2PXgqlfJGSs wnVypRt3Ve26Ucg+vAeZ2OF/YRTxuYbsoJWN/VpzU/tq+0ochL5OAN2yCtwtDBc+BHH1 OMFGEVf/b+gd9q1xI4y04goDoCI1skF+pybOZy9/CnDXvwaVHmFhESRdof+2qsjn+y8D Id/0cbz+w4u4TXxKUI08Qh8+b6Lu+AZAW2sarv2QsEt2Btd1FiehRP1DJe+z3W723Lu3 a2DP9Y58eXBT1z3FF0FZzfRbtVfB4VgtY4Y54LqKinqr6xUVEfeXspbkCZrI9NtWGLRB 3+TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=lgVWkPrWP1XWoPa+dj0908s7trRWSBUtAulmXbbAkzU=; b=MKh70oeLGZ2VOk8R9jHvqwV0lNgN42lHrbfeUiy4nSlV31LqL7lFvcgmZNyHm/rrGz elMLwfX3UOe0fvCaEq+aUdzmysD6G3/tvIjNctluinnDxwS67Y9lQxQ2Sp6hRCLaKqrC bcuOfsiBPfGfMLqtR7K/zDWtVu1F+b1PMfL19ujOaO2I3vlxSQaRLbxDhKASvSEOozsx SnindIX7QeNmfD1YUgijkZFOPjvqNuauLLi3AaAHO0hhhtc0G4P/Zu/0nBmgAG/eY5fo 3RB/cMRk57kUnkIelnM1cCLsyYjmqzydyHNAVu4tMoFLgMmZ6a5m+xK4bdjP1QPpdqXA FVCQ== X-Gm-Message-State: AD7BkJKeOzKCy7RbqsOJV5+NQSDY4L3Cc8JoKMhTximC4hmaVPCwUGGMNBHiyaXqt9pu1mXCVNYuD5wcVFsuMg== MIME-Version: 1.0 X-Received: by 10.140.19.52 with SMTP id 49mr4933972qgg.103.1457624333143; Thu, 10 Mar 2016 07:38:53 -0800 (PST) Received: by 10.55.106.5 with HTTP; Thu, 10 Mar 2016 07:38:53 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Thu, 10 Mar 2016 18:38:53 +0300 Message-ID: Subject: Re: EFI zfs loader and beadm? From: Andrey Fesenko To: krad Cc: Eric van Gyzen , "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 15:38:54 -0000 On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > As Eric said you cant have /boot on a separate dataset as the whole loader > bootstrap isnt designed too look for it on the dataset defined by bootfs. > Remember no other datasets are mounted at that stage of the bootstrap. > > You could maybe bodge something by manually playing around with the bootfs > property, symlinks and rootfs variables in the loader.conf. But why would > you want to do this? It's more work and non standard, and will break a lot? > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: >> >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: >> > presumably it boots now? >> > >> > On 10 March 2016 at 11:01, Andrey Fesenko wrote: >> >> >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: >> >> > Make sure you are running the latest snapshot of current or 10.3 as >> >> > well, as >> >> > the MFC commits were in early February for 10-stable >> >> > >> >> >> >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> >> >> efiwpool/ROOT/init my scheme work fine too. >> >> >> /usr /var /home and other included in BE for consistent boot system >> >> >> (CURRENT world may not boot with kernel other rev), and old home >> >> >> snapshot sometimes useful for backup/restore >> >> >> _______________________________________________ >> >> >> >> % uname -a >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: >> >> Wed Mar 9 01:16:17 MSK 2016 >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 >> > >> > >> >> My current working config >> % mount >> .... >> >> This work fine, booted, beadm create new env, activate them, see boot >> menu and select BE. >> >> % beadm list >> BE Active Mountpoint Space Created >> init - - 420.7M 2016-03-09 02:57 >> init0 NR / 35.9G 2016-03-10 05:00 >> >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) >> system not booted, efi loader (first stage) see only my pool, not >> found /boot/loader.efi > > It probably does not matter, as bootfs have snapshots (BE), just wanted to make it more clear (having taken significant mountpoint /boot, /usr, /var... in zfs dataset) and was surprised why the system does not boot It is clear that as long as the functionality is experimental and under development, but would like to see where the full instructions on its implementation / restrictions, at least as early as has been described https://wiki.freebsd.org/RootOnZFS