From owner-freebsd-stable@freebsd.org Tue Jan 31 14:35:08 2017 Return-Path: Delivered-To: freebsd-stable@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 E0412CC9751 for ; Tue, 31 Jan 2017 14:35:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (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 B762D949 for ; Tue, 31 Jan 2017 14:35:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x244.google.com with SMTP id f200so4114106itf.3 for ; Tue, 31 Jan 2017 06:35:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=aLJf5n+YlScvGOg1GyBl2MEjRtghqezufuSUhbr5s/8=; b=CQVxEOObl+1Ivi0YGQuZDpbC+AFXarrDR0ZR1ra51BEhbrzJwmhoeIjPpt+iGhT3oB N86atZhNmQRyMNKtbkhy0k6hv/L6LZ17r9xQJnOXQgwjBhi2RdBfGw9iVvDFc3arY6rr CAqQqe78V/L5s6qamF5rXP+3UfihuWhBbWC8iUrPloocLQguWa7tu+9dwSBK4IboqZ9a XtHCzEdD5ZOBrNs9pWKk4rBWml7sFf9U5a9ZQIPnFkt62whopThHwJVZ+2dpCNXSP7Xj u2+JQ62uZc6AVmDjI4ufFZas0SKyPgo1vaIa2n7U9kax5zV15/u917NaaUJm4iJJfGh3 Vh3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=aLJf5n+YlScvGOg1GyBl2MEjRtghqezufuSUhbr5s/8=; b=WhqtA4zxcWwxUZcbJ2UeAeK79Blhtz4L2XkswOzcu7+7W+rvCu604VBXNAyPELxmDo dBsxkwknV5x+HSEY6LOlAUDhpdJtSycBV/23y2T/SbqcLvUYTdq5NaW56QaEV9/OAT7Y Wn5zu588zQ2hWHR6uUVaUz83o0AvOUGOW0CorcmSiVnwCekwtOEW3eEcVh7pB0se2tkh 0+NQpHwKn+6VJYaG5U65BsJrahGFL0BA4VFGxuiKNSggQPaO7ZjpR9oE99fvQuPLyVFt PIYID9RjLO+5sixZI1k5IxG3NI7ZgOU+36dcxlFaWxKw1CWwZgSpO7WlZ8szYPiRAChx xYww== X-Gm-Message-State: AIkVDXKwq1msRV/SjHaTq3bQPc8rUN1gHCBlBiFxaXmFWZU9OS8g5wQ3VXvQcJ+laUp83WzAfh3IYgttAwlCxg== X-Received: by 10.36.93.213 with SMTP id w204mr21740793ita.60.1485873307915; Tue, 31 Jan 2017 06:35:07 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.145.217 with HTTP; Tue, 31 Jan 2017 06:35:07 -0800 (PST) X-Originating-IP: [69.53.245.200] In-Reply-To: References: <20170129141244.GA63867@in-addr.com> <851efa44-0607-231f-0905-8f9c96a36237@ish.com.au> From: Warner Losh Date: Tue, 31 Jan 2017 07:35:07 -0700 X-Google-Sender-Auth: RVWPqc9D2t612d0npMJ_KydF338 Message-ID: Subject: Re: Boot partition size To: Andreas Nilsson Cc: krad , FreeBSD Stable , Aristedes Maniatis Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 31 Jan 2017 14:35:09 -0000 The UEFI standard suggests something large like 100MB. There are a number of firmware updating programs that run as .efi images. It would be prudent to allow more than the bare minimum in case you wind up needing them down the line. boot1.efi is likely to grow significantly in the future. Maybe not 100x, a 1MB is likely once it has all the features it needs. 10MB might be a safe upper bound. Warner On Tue, Jan 31, 2017 at 7:00 AM, Andreas Nilsson wrote: > Well, 100mb might be relevant if you ever want to dual-boot. The relevant > efi file seems to be < 100k > > It may go up in size, but I doubt we will see a 100x increase. > > /A > > On Tue, Jan 31, 2017 at 1:03 PM, krad wrote: > >> Its worth noting you should also go for GPT layout and have a 100meg or so >> partition provisioned as well so you can do a uefi boot. Even if you arent >> going to use it right now. >> >> >> On 30 January 2017 at 03:41, Aristedes Maniatis wrote: >> >> > On 30/1/17 2:20pm, Freddie Cash wrote: >> > > And, you may be able to do that on the existing disks, as ZFS now >> leaves >> > a MB or two of "slack space" at the end of the device used in the vdev. >> > This allows for using drives/partitions that are the same size in MB but >> > have different numbers of sectors. This was an issue on the early ZFS >> days. >> > > >> > > So, you may be able to resize the freebsd-zfs partition by a handful of >> > KB without actually changing the size of the vdev. >> > >> > >> > Brilliant, thank you. That worked a treat with a new boot size of 256k. >> > >> > >> > Note that this page: https://wiki.freebsd.org/ >> RootOnZFS/GPTZFSBoot/Mirror >> > needs to be adjusted. This line: >> > >> > gpart add -b 34 -s 128k -t freebsd-boot ad0 >> > >> > needs to instead be >> > >> > gpart add -a 4k -s 512k -t freebsd-boot ad0 >> > >> > >> > I don't have edit rights. Probably someone needs to clean up and merge >> > many of these pages: https://wiki.freebsd.org/RootOnZFS/ >> > >> > >> > Ari >> > >> > >> > >> > -- >> > --------------------------> >> > Aristedes Maniatis >> > CEO, ish >> > https://www.ish.com.au >> > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >> > >> > >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"