Date: Sun, 23 Dec 2018 22:19:53 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 233657] bectl siliently fails on i386 Message-ID: <bug-233657-227-LYW0smsLgG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233657-227@https.bugs.freebsd.org/bugzilla/> References: <bug-233657-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233657 --- Comment #3 from Rob <rob.fx907@gmail.com> --- (In reply to Philip Homburg from comment #2) I don't know how it would. Given that no error messages are produced, my hunch is bectl is failing to initialize 'bectl' uses libbe(3) to initialize a boot environment to work from. The following is a description about 'libbe_init()' from the libbe(3) man page: The libbe_init() function takes an optional BE root and initializes libbe, returning a libbe_handle_t * on success, or NULL on error. If a BE root is supplied, libbe will only operate out of that pool and BE root. An error may occur if: /boot and / are not on the same filesystem and device, libzfs fails to initialize, The system has not been properly booted with a ZFS boot environment, libbe fails to open the zpool the active boot environment resides on, or libbe fails to locate the boot environment that is currently mounted. That may help you trouble-shoot the cause. Another thing to try is, pass the root boot environment (i.e. zroot/ROOT) to bectl explicitly. This is undocumented but, you can pass the '-r' flag before any of the 'bectl' commands (create, list, destroy, etc.). Here's an example: To create boot environment named 'bootenv' under the boot root zroot/ROOT # bectl -r zroot/ROOT create bootenv To list a boot environment under zroot/ROOT # bectl -r zroot/ROOT list I'm curious what you come up with. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233657-227-LYW0smsLgG>