Date: Fri, 27 Jun 2025 17:55:13 -0600 From: Alan Somers <asomers@freebsd.org> To: Gleb Smirnoff <glebius@freebsd.org> Cc: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: Closing: June 2025 stabilization week Message-ID: <CAOtMX2gvSi7CeA=yxr3dXkFNptHhs2f_jFNdOJUwaE5MpQJ7tw@mail.gmail.com> In-Reply-To: <aF8ONK2qb3VJBjqL@cell.glebi.us> References: <aFkJwZgyZXgZkXiX@cell.glebi.us> <aF8ONK2qb3VJBjqL@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Jun 27, 2025 at 3:34 PM Gleb Smirnoff <glebius@freebsd.org> wrote: > On Mon, Jun 23, 2025 at 01:01:05AM -0700, Gleb Smirnoff wrote: > T> This is an automated email to inform you that the June 2025 > stabilization week > T> started with FreeBSD/main at main-n278153-b2e0dfc808c1, which was > tagged as > T> main-stabweek-2025-Jun. > > This snapshot had 3 regressions identified, 2 of which are already > addressed: > > 1) The disabled pathname expansion in rc(8) broke certain setups. The > offending change had been reverted. Users of the stabweek snapshot > are advised to cherry-pick: d783591a7deb and 9c014cc25c43 > > 2) libtpool.so.2 was erroneously put into ObsoleteFiles.inc. A run of > 'make delete-old-libs' or a fresh install of the stabweek snapshot > ended in broken boot from a ZFS root. The problem was fixed by > b5962a183756. This revision is also advised for cherry-pick. > I think you mean "libtpool.so.2 was erroneously moved from /lib to /usr/lib". > > 3) Changes in OpenZFS induce performance degradation. See: > > https://github.com/openzfs/zfs/pull/17445#issuecomment-3009891003 > > This issue is still not resolved. Once resolved the StabWeeks wiki > page will reflect that: https://wiki.freebsd.org/StabWeeks > > Note: in the Tuesday email I reported that at Netflix A/B testing we see > increased wired memory use. This appeared to be a result of the conflict > resolution mistake and does not apply to vanilla FreeBSD. > > -- > Gleb Smirnoff > [-- Attachment #2 --] <div dir="ltr"><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Jun 27, 2025 at 3:34 PM Gleb Smirnoff <<a href="mailto:glebius@freebsd.org">glebius@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Jun 23, 2025 at 01:01:05AM -0700, Gleb Smirnoff wrote:<br> T> This is an automated email to inform you that the June 2025 stabilization week<br> T> started with FreeBSD/main at main-n278153-b2e0dfc808c1, which was tagged as<br> T> main-stabweek-2025-Jun.<br> <br> This snapshot had 3 regressions identified, 2 of which are already<br> addressed:<br> <br> 1) The disabled pathname expansion in rc(8) broke certain setups. The<br> offending change had been reverted. Users of the stabweek snapshot<br> are advised to cherry-pick: d783591a7deb and 9c014cc25c43<br> <br> 2) libtpool.so.2 was erroneously put into ObsoleteFiles.inc. A run of<br> 'make delete-old-libs' or a fresh install of the stabweek snapshot<br> ended in broken boot from a ZFS root. The problem was fixed by<br> b5962a183756. This revision is also advised for cherry-pick.<br></blockquote><div><br></div><div>I think you mean "libtpool.so.2 was erroneously moved from /lib to /usr/lib".</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> 3) Changes in OpenZFS induce performance degradation. See:<br> <br> <a href="https://github.com/openzfs/zfs/pull/17445#issuecomment-3009891003" rel="noreferrer" target="_blank">https://github.com/openzfs/zfs/pull/17445#issuecomment-3009891003</a><br>; <br> This issue is still not resolved. Once resolved the StabWeeks wiki<br> page will reflect that: <a href="https://wiki.freebsd.org/StabWeeks" rel="noreferrer" target="_blank">https://wiki.freebsd.org/StabWeeks</a><br>; <br> Note: in the Tuesday email I reported that at Netflix A/B testing we see<br> increased wired memory use. This appeared to be a result of the conflict<br> resolution mistake and does not apply to vanilla FreeBSD.<br> <br> -- <br> Gleb Smirnoff<br> </blockquote></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2gvSi7CeA=yxr3dXkFNptHhs2f_jFNdOJUwaE5MpQJ7tw>