Bug 257492 - bectl: libbe_init("") failed
Summary: bectl: libbe_init("") failed
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 13.0-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2021-07-29 18:59 UTC by dougs@dawnsign.com
Modified: 2021-09-05 15:40 UTC (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description dougs@dawnsign.com 2021-07-29 18:59:28 UTC
Upgraded all of my servers to 13.0-RELEASE. On two of my servers are the following zfs list:

[root@fornax 29.Jul 10:56am ~]# zfs list
tank           20.0G   964G       23K  none
tank/root      20.0G   964G     18.3G  /
tank/root/tmp  47.5K   964G     47.5K  /tmp
tank/root/var  1.68G   964G     1.68G  /var
[root@fornax 29.Jul 10:59am ~]# 

Note the two-part zpool name.

When calling bectl, I receive the following error:

[root@fornax 29.Jul 10:38am ~]# bectl list
libbe_init("") failed.

My filesystems are like this:

[root@fornax 29.Jul 10:59am ~]# df
Filesystem     1K-blocks     Used      Avail Capacity  Mounted on
tank/root     1030259566 19201838 1011057728     2%    /
devfs                  1        1          0   100%    /dev
tank/root/tmp 1011057775       47 1011057728     0%    /tmp
tank/root/var 1012819830  1762102 1011057728     0%    /var
[root@fornax 29.Jul 11:01am ~]# 

None of the servers I control using three-part zpool names exhibit such errors.

I used Martin Matuska's mfsbsd to install these two servers and that is how I ended up with these default filesystem naming scheme. When using the FreeBSD installers, the default root filesystem name is zroot/ROOT/default whereas mfsbsd produces tank/root.

Is there a workaround?
Comment 1 Kyle Evans freebsd_committer 2021-07-29 19:05:29 UTC
I believe this review should fix it: https://reviews.freebsd.org/D30636 (see PR 253445)

I'll get back to that soon-ish, sorry. :-(
Comment 2 Robert Wing freebsd_committer 2021-07-30 18:12:39 UTC
(In reply to dougs@dawnsign.com from comment #0)

Have you tried running the patch I suggested in your other bug report?