Date: Fri, 11 Mar 2022 00:38:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262477] bectl.8: Mention a possible reboot -r failure after renaming Message-ID: <bug-262477-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262477 Bug ID: 262477 Summary: bectl.8: Mention a possible reboot -r failure after renaming Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: bugs@FreeBSD.org Reporter: jlduran@gmail.com CC: doc@FreeBSD.org beadm added a change in which the kenv variable `vfs.root.mountfrom` is modified to reflect the new name after a boot environment rename: https://github.com/vermaden/beadm/commit/023d18ea431dab7aa5c513e09b0e7abc61= 072817 I would prefer not to modify the kenv automatically, however I believe it w= ould be good to warn the user if issuing `reboot -r` by mentioning it in the man page. How to reproduce: # bectl list BE Active Mountpoint Space Created default NR / 500M 2022-03-10 12:00 # kenv vfs.root.mountfrom zfs:zroot/ROOT/default # bectl rename default newbe # reboot -r Trying to mount root from zfs:zroot/ROOT/default []... Mounting from zfs:zroot/ROOT/default failed with error 2; retrying for 3 mo= re seconds Mounting from zfs:zroot/ROOT/default failed with error 2. Loader variables: vfs.root.mountfrom=3Dzfs:zroot/ROOT/default Manual root filesystem specification: <fstype>:<device> [options] Mount <device> using filesystem <fstype> and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:zroot/ROOT/default cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) <empty line> Abort manual input mountroot> zfs:zroot/ROOT/newbe Trying to mount root from zfs:zroot/ROOT/newbe []... --=20 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-262477-227>