From owner-freebsd-hackers@freebsd.org Fri Mar 11 10:00:34 2016 Return-Path: Delivered-To: freebsd-hackers@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 4D34AACC9D1; Fri, 11 Mar 2016 10:00:34 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (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 058FF687; Fri, 11 Mar 2016 10:00:34 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-qg0-x235.google.com with SMTP id u110so93791342qge.3; Fri, 11 Mar 2016 02:00:33 -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-transfer-encoding; bh=apbuhY39hl/OMjMpwv+ebLv/4IKyhUX4+pRosHbE/Jg=; b=x/y1NpS9Lf7i3juL7serN/Pd3pqhHGX80r+HB7a+Fan6qbSbvKmE7IzSOrP+eeb8jP aTZXAskhLFCAUvRpXgUfm+TLEMdjCh2VJQ7kLsRUPCGQDxoCfhSpDsjJxuJda/0eu7Jl EaFF/3aNylq7vJ2OSR+D0JLHpQQy4dafUJ/Q3bSIYAfRzryFvtfLIxD1nI/FxJYE1NYI WZCpVBK4Dyy7cYGGPJc8/SzKQ/F8F2skIVYtO4qp0Rzx7u97DkRX+4UH8rAdkBL4pfpy 8xE6i9ZXrNXcMnPxqALHEu1LHPzL6qZZPzSNt2A2elhIQaQizacWKX2soqYaNCUh+laa WBbw== 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:content-transfer-encoding; bh=apbuhY39hl/OMjMpwv+ebLv/4IKyhUX4+pRosHbE/Jg=; b=huUhSvXovNooTeAIrj3nQmGvc43VtYH5GxejcyLAtiylRkcdJtvDAE0etS4wCm7WzT ZC07JG5hV2gpm7W9KS9O6mo/+n/gyBkSikW/jIyogk+FYwT4fEZXH/kADo4kzunMw40H 0X7DfK9Y3hrAi2QnlSMQ08ogxEaznrj7Bz8oO8S58ldxaqbPXUh665OX0mJbjeNHR4tG qH5PM5WenseBxlMwLly/Jt1qB6Zb2r0vgmB+igks7f5crnfAEX0Tn26eFjTjrWy2n7Vm RpRw0Y63wfQGSKDFEBM8inLV2n4Vm7WPmmxhm7wL/kd7DHc7LmjPH5Suf/9b3wUNzy4J 6few== X-Gm-Message-State: AD7BkJIPvTrOf1cCwN/fMZNQqnmKKc0Z+p2Q3Txi/QM2iHD8FPmlesVS77xYE7itJkjrwL5iAmn8NaLyd+GOZw== MIME-Version: 1.0 X-Received: by 10.140.138.209 with SMTP id 200mr10888327qhk.100.1457690433032; Fri, 11 Mar 2016 02:00:33 -0800 (PST) Received: by 10.55.106.5 with HTTP; Fri, 11 Mar 2016 02:00:32 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Fri, 11 Mar 2016 13:00:32 +0300 Message-ID: Subject: Re: EFI zfs loader and beadm? From: Andrey Fesenko To: krad Cc: =?UTF-8?Q?Trond_Endrest=C3=B8l?= , "freebsd-hackers@freebsd.org" , freebsd-current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 10:00:34 -0000 On Fri, Mar 11, 2016 at 10:52 AM, krad wrote: > Its also worth pointing that if you decouple the userland from the kernel > files you no longer have a boot environment, as all the basic stuff to bo= ot > the os isn't contained within the bootfs. I'm still struggling to see why > /boot needs to be on a different dataset, its just a bit of a linuxism. > > On 10 March 2016 at 19:23, Trond Endrest=C3=B8l > wrote: >> >> On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: >> >> > 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 bootstra= p. >> > > >> > > 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 bo= ot >> > >> 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 >> >> If you keep /boot as a separate dataset/filesystem, with >> efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not >> see a /boot directory inside that dataset. The files and directories >> from /boot will be presented as living in /, the local root directory >> of that dataset. >> >> You could create a /boot/boot symlink pointing to . (dot), but it's >> better to let /boot be part of the regular boot environment, pretty >> similar to what you would find on a UFS system using a separate root >> filesystem. >> why? On the contrary, my scheme involves the entire system as a single BE (including home) > linuxism Is unlikely, to rather an attempt to use all the features ZFS. ZFS also many possible settings for each dataset/FS (compression, atime, exec......) Probably for /boot many of them unnecessary, but such separate extra snapshots, can would not be harmful