Date: Tue, 29 Jan 2019 16:18:17 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 221077] Boot from ZFS fails following freebsd-update Message-ID: <bug-221077-3630-3Jm31QN6jy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221077-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-221077-3630@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=3D221077 Warner Losh <imp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #21 from Warner Losh <imp@FreeBSD.org> --- Yes. Due to the extreme space limitations of boot2, printf in it has been shaved to the bone. boot2 doesn't support ZFS at all, but is only for UFS s= ince it lives in the UFS boot block area. But for *gptboot, we use the printf in libsa/printf.c, which at least prete= nds to support 'j' modifiers (and the pretense appears to be quite good from my reading of it). So it's quite odd to see 'u' printed there. A quick grep of= the symbols for the .o's brought in shows they are all U. There is a zfs_printf, but it just calls printf and returns 0. --=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-221077-3630-3Jm31QN6jy>