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 <kraduk at gmail.com> 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 <ari at ish.com.au> 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 at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >
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 <andrnils at gmail.com> 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 <kraduk at gmail.com> 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 <ari at ish.com.au> 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 at freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >> > _______________________________________________ > freebsd-stable at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
Are we really that worried about 90-99 MB when we are talking about many TB drives? Even the entry-mid range SSD are in the region of 256-512 GB these days? On 31 January 2017 at 14:35, Warner Losh <imp at bsdimp.com> wrote:> 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 <andrnils at gmail.com> > 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 <kraduk at gmail.com> 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 <ari at ish.com.au> 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 at 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 at freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org > " >