src/lib/libbe, branch release/13.1.0

bectl: push space-in-name check down into libbe

2022-04-06T14:32:51Z

This check was previously in `create` only, not applying to renames. It should really be applied at the libbe level, so that we can avoid writing about this restriction over and over again. While we're here: `bectl rename` always succeeds, even when it doesn't. Start returning the error. Approved by: re (gjb) Reported By: Christian McDonald (cherry picked from commit dadb9c70938c4ae2c260f6af65752c67ac752284) (cherry picked from commit 227e52a9c0b0be9656757fec47a2648f5619bf67)

libbe: fix be_mounted_at() with props after bootonce

2022-04-06T14:32:44Z

propinfo.bootonce was filled with garbage, leading to a segfault later during prop building. Initialize it to NULL. Approved by: re (gjb) (cherry picked from commit d155d8e138563c0b39c658684e6a4fe6e2e36f8a) (cherry picked from commit 6ce8e35cead46048d9ae3c1dabafe1ef4ed26f97)

libbe: pull props for the correct dataset in be_mounted_at()

2022-04-06T14:32:31Z

The props feature to this API was added as a "just in case", with no planned consumer. It turns out that it was implemented incorrectly, tapping out props for the BE root (BE's parent) rather than the BE itself in all cases. Fetch properties for the dataset that's actually mounted at the queried path. Approved by: re (gjb) Reported by: Christian McDonald (cherry picked from commit 31190aa02eef05b1b58ba89212dc8c8738770e37) (cherry picked from commit bed9c972aee7aa5ac916f24d60d9dbd109897856)

When be_activate() turns on a new boot environment, it always deactivates

2021-01-08T17:23:16Z

the current one first. And if it fails to do so, it abandons activation. However, with the new bootonce feature, there is a legitimate case when a pool doesn't have "bootfs" property set. Check for this case before calling be_deactivate(). Reviewed by: kevans

pkgbase: Move bectl to the runtime package

2021-01-04T15:17:12Z

runtime contain what is needed to boot in single user and repair a system, bectl could be handy to have in this situation. Differential Revision: https://reviews.freebsd.org/D27708

libbe(3): install MLINKS for all of the functions provided

2020-10-18T23:58:40Z

MFC after: 1 week

libbe(3): document be_snapshot()

2020-10-18T23:42:00Z

While toying around with lua bindings for libbe(3), I discovered that I apparently never documented this, despite having documented be_is_auto_snapshot_name that references it. MFC after: 1 week

libbe(3): const'ify a couple arguments

2020-10-18T23:32:47Z

libbe will never need to mutate these as we either process them into a local buffer or we just don't touch them and write to a separate out argument. MFC after: 1 week

loader: zfs should support bootonce an nextboot

2020-09-21T09:01:10Z

bootonce feature is temporary, one time boot, activated by "bectl activate -t BE", "bectl activate -T BE" will reset the bootonce flag. By default, the bootonce setting is reset on attempt to boot and the next boot will use previously active BE. By setting zfs_bootonce_activate="YES" in rc.conf, the bootonce BE will be set permanently active. bootonce dataset name is recorded in boot pool labels, bootenv area. in case of nextboot, the nextboot_enable boolean variable is recorded in freebsd:nvstore nvlist, also stored in boot pool label bootenv area. On boot, the loader will process /boot/nextboot.conf if nextboot_enable is "YES", and will set nextboot_enable to "NO", preventing /boot/nextboot.conf processing on next boot. bootonce and nextboot features are usable in both UEFI and BIOS boot. To use bootonce/nextboot features, the boot loader needs to be updated on disk; if loader.efi is stored on ESP, then ESP needs to be updated and for BIOS boot, stage2 (zfsboot or gptzfsboot) needs to be updated (gpart or other tools). At this time, only lua loader is updated. Sponsored by: Netflix, Klara Inc. Differential Revision: https://reviews.freebsd.org/D25512

Skip armv7 bectl tests on CI; they deadlock (""KSTACK_PAGES is 2").

2020-09-14T10:35:39Z

PR: 249229 Sponsored by: DARPA