bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
I'm still on r364030 using sysutils/openzfs 2020081800 (compiled from ports) pkg info -s openzfs openzfs-2020081800 15.3MiB I currently only have 1 BE and would like to attempt to upgrade to anything past r364746 I don't use encryption, won't attempt an 'zpool upgrade' of zroot so think I should be safe to move forward. # bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r364030-OpenZFS zroot/ROOT/r364030-OpenZFS NR / 15.2G 2020-08-22 22:46 create new BE # bectl create r364030-OpenZFS2 root@harbinger:~ # bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r364030-OpenZFS zroot/ROOT/r364030-OpenZFS NR / 15.2G 2020-08-22 22:46 r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 r364030-OpenZFS2 zroot/ROOT/r364030-OpenZFS2- - 8K 2020-08-30 19:23 zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 activate new BE # bectl activate r364030-OpenZFS2 cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem Did not successfully activate boot environment r364030-OpenZFS2 # zfs get origin zroot/ROOT/r364030-OpenZFS2 NAME PROPERTY VALUE SOURCE zroot/ROOT/r364030-OpenZFS2 origin zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 - Despite the warning/erros messages listed a 'bectl list' does show that the new BE will be active on reboot # bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r364030-OpenZFS zroot/ROOT/r364030-OpenZFS N / 15.2G 2020-08-22 22:46 r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 r364030-OpenZFS2 zroot/ROOT/r364030-OpenZFS2R - 8K 2020-08-30 19:23 zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 However the boot fails dropping me to the mountroot prompt. Luckily activating r364030-OpenZFS again is not a problem and the system will happily boot from that again after attempting to boot from r364030-OpenZFS2. So now I have only 1 working BE and it feels a bit tricky to try an upgrade in place. What's the best advice here? I could switch back to base ZFS in this active BE, see if the system will be able to import zroot and mount all my datasets and boot, then try to create another BE using base ZFS and then attempt to update. -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Does FreeBSD have an assigned Internet OID?
Poul-Henning Kamp wrote: >Rick Macklem writes: >> Poul-Henning Kamp wrote: > >> Is https://reviews.freebsd.org/D26225 >> sufficient to allow me to use 1.3.6.1.4.1.2238.1.1.1 for a user@domain >> name in this otherName component of subjAltName in the X.509 cert? >> (I didn't list the UserName as the first item of the subtree. Should I?) > >You should add a comment about how suballocations (if allowed) happens >under that branch. I think it is easiest to do them in this file. I have added an entry for it. >> Do I need to update the date/time for LAST-UPDATED and REVISION >> when I commit it, I'd guess? > >Yes please. I've updated https://reviews.freebsd.org/D26225 If you could review this, it would be appreciated, rick -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71
On Fri, 28 Aug 2020 13:16:05 +0200 Mateusz Guzik wrote: > On 8/28/20, Hartmann, O. wrote: > > On Fri, 28 Aug 2020 12:31:21 +0200 > > Mateusz Guzik wrote: > > > >> Can you show more of the log? > >> > >> When you installkernel you should see: > >> mkdir -p /boot/kernel > >> install -p -m 555 -o root -g wheel kernel /boot/kernel/ > > > > These lines are seen right after the beginning of "make > > installkernel". > >> mkdir -p /usr/lib/debug/boot/kernel > >> install -p -m 555 -o root -g wheel kernel.debug > >> /usr/lib/debug/boot/kernel/ > > > > I wouldn't expect these lines according to my /etc/src.conf, since I > > disbaled debugging and installing debugging infos. > >> > >> Did these succeed? Do these dirs exist now? > > > > It is not existent, as expected: > > > > > > # ll /usr/lib/debug/boot/kernel/ > > ls: /usr/lib/debug/boot/kernel/: No such file or directory > > > > Ok. I recently made changes to the namecache, which if buggy, could > have resulted in woes like the above. > > Thus it looks like the newly imported zfs does not respect > WITHOUT_DEBUG_FILES. Even in r364973 the problem still remains. Disabling option WITHOUT_DEBUG_FILES in src.conf is exhausting the /usr/obj partition (using UFS/FFS) and no option. Got now several boxes having "make installkernel" issued with a running system but incomplete kernel installation, as buildkernel suggested a clean build. Can this be fixed, please? > > >> > >> On 8/28/20, Hartmann, O. wrote: > >> > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 > >> > 16:10:50 CEST 2020 amd64), /usr/src at revision 364907, > >> > installkernel fails now due to an error as shown below. For the > >> > record, "options ZFS" ist statically in the kernel config file. > >> > > >> > Also deleting /usr/obj and restarting buildworld and buildkernel > >> > from scratch doesn't solve the problem. The buildworld and > >> > buildkernel mutually finish without error (I do not see any on > >> > the console), installworld also finishes fine, but installkernel > >> > not. > >> > > >> > /etc/src.conf looks as follows: > >> > > >> > [...] > >> > CPUTYPE?= native > >> > # World > >> > CFLAGS+=-O3 > >> > #CFLAGS+= -DNDEBUG > >> > # Kernel > >> > COPTFLAGS+= -O3 > >> > #COPTFLAGS+=-DNDEBUG > >> > #CXXFLAGS+= -std=c++17 > >> > WITH_CLANG_EXTRAS= YES > >> > WITH_LLDB= YES > >> > #WITH_BSD_GREP= YES > >> > WITH_OFED_EXTRA=YES > >> > WITH_NAND= YES > >> > #WITH_CTF= YES > >> > WITH_SVN= YES > >> > WITH_BEARSSL= YES > >> > WITH_PIE= YES > >> > WITH_SORT_THREADS= YES > >> > WITH_ZONEINFO_LEAPSECONDS_SUPPORT= YES > >> > MALLOC_PRODUCTION= YES > >> > WITHOUT_ASSERT_DEBUG= YES > >> > WITHOUT_TESTS= YES > >> > WITHOUT_PROFILE=YES > >> > WITHOUT_DEBUG_FILES=YES > >> > WITHOUT_REPRODUCIBLE_BUILD= YES > >> > > >> > [...] > >> > > >> > Debugging facilities are disabled as src.conf indicates. > >> > > >> > [...] > >> > install -T release -o root -g wheel -m 555 xz.ko > >> > /boot/kernel/ ===> zfs (install) > >> > install -T release -o root -g wheel -m 555 zfs.ko /boot/kernel/ > >> > install -T dbg -o root -g wheel -m 555 zfs.ko.debug > >> > /usr/lib/debug/boot/kernel/ > >> > install: /usr/lib/debug/boot/kernel/: No such file or directory > >> > *** Error code 71 > >> > > >> > Stop. > >> > make[4]: stopped in /usr/src/sys/modules/zfs > >> > *** Error code 1 > >> > *** Error code 1 > >> > > >> > >> > > > > > > pgp9ygOHkxprd.pgp Description: OpenPGP digital signature
Re: documentation on release build process change (svn -> git)?
Dear Michael , Your messages are classified as spam because GMail is not able to verify that their origin is the above address . I have tried to send this message to Michael Butler GMail responded as approximately "The address could not be found." . Mehmet Erol Sanliturk On Sun, Aug 30, 2020 at 12:48 AM Glen Barber wrote: > On Sat, Aug 29, 2020 at 09:43:25PM +, Glen Barber wrote: > > On Sat, Aug 29, 2020 at 09:40:17PM +, Glen Barber wrote: > > > On Sat, Aug 29, 2020 at 09:30:02PM +, Glen Barber wrote: > > > > On Sat, Aug 29, 2020 at 05:21:16PM -0400, Michael Butler wrote: > > > > > On 8/29/20 5:17 PM, Glen Barber wrote: > > > > > > On Sat, Aug 29, 2020 at 04:38:05PM -0400, Michael Butler wrote: > > > > > >> The build-from-existing mode fails with .. > > > > > >> > > > > > >> imb@vm01:/usr/src/release> sudo ./release.sh -c > release-i386.conf > > > > > >> fatal: not a git repository (or any parent up to mount point > /usr) > > > > > >> Stopping at filesystem boundary > (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > > > > > >> umount: /usr/local/release-builds/i386/dev: not a file system > root directory > > > > > >> > > > > > > > > > > > > Here's the fun part - Which revision was this? > > > > > > > > > > The host system is check-out from SVN r364964, > > > > > > > > > > > > > Can you please try the attached patch against your release.sh? > > > > > > > > > > Nevermind, I see the problem. Standby. > > > > > > > r364966 should fix it. Thank you again for your help here. > > > > Sigh. r364968 should *really* fix it.. > > Is it Friday yet? > > Glen > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
