From nobody Sun Sep 08 15:24:57 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X1v0X6pJSz5V9tY for ; Sun, 08 Sep 2024 15:25:00 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout1-smtp.messagingengine.com (fout1-smtp.messagingengine.com [103.168.172.144]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X1v0X2FWmz4H04 for ; Sun, 8 Sep 2024 15:25:00 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=2EeS7ZIF; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="K kTEHS9"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.144 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-08.internal (phl-compute-08.phl.internal [10.202.2.48]) by mailfout.phl.internal (Postfix) with ESMTP id D82531380212 for ; Sun, 8 Sep 2024 11:24:58 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-08.internal (MEProxy); Sun, 08 Sep 2024 11:24:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1725809098; x=1725895498; bh=KC9L3SOTMdt5GmiMVhC/DVyHRonUygxcCGBGjzs7saI=; b= 2EeS7ZIFAJfLQQg5CyIJq/duckRaWh2gG0XOb2EMcR7fdeq7L8bIsuWNBO5bBNN0 +AW2vffDPkyr8m92AhwwCrrU0iwvKZqkVODNEYA5xVB9oXitlqBQIX8slccFNP8F nJ8gdJeVwSdxBWXxQy9i8cFrufNhwJUjx4KyXDDMiFfDTCWzahLULgaKFcFYz/2q HIwZJ2IV0ETLj3fkRlRMGtiE/W6O4E+vvgCF9IDVPpkYE7FaZdfwD7/sNyjHF+yE 2jvNQRThC+7vcUSFkWoevCnO4uHjjQmqa+o91ugInSgtzypZmleixIxCDj4/IPTo I6lPCWjatpEHyrONhMr+PA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1725809098; x= 1725895498; bh=KC9L3SOTMdt5GmiMVhC/DVyHRonUygxcCGBGjzs7saI=; b=K kTEHS9xM+IjdtwkFabyv56J5XqDhMKne60By6PhpHxCHx0YAa1WuVW7rfykN4mp+ xsb8nGxsU1zegxjgrVpDZLifBz/f5EzRAXo0mZuKLG3gdSOUr6oaomUxEkKokOz8 E2Z+s77ayJdaPMHuCWy4N0jBNkNQrAQbBnlucH/HzbP2G/OnYj7zR3P1E7RNAUsu Q/lDP8OeayqcYd239e8JMSylQpddKqO2pOZ6aCUNh6CxCQwuun0y77Mbt3Xn735F fvp8Cy8QsIfG8ZRM8gTMDmVeTauc75ZE9dEJ5U/foROyqq0545JRgvf8Ytky80DQ Su6F0QoCCKi4SM+0Indwg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudeihedgkeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuf fkfhggtggugfgjsehtkeertddttdejnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdq mhdrfhhmqeenucggtffrrghtthgvrhhnpeduteevgeeggeevieetvdduudetfffffffhte ejgffggeevjeffieduteeftedvkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfhhmpdhnsggprhgtphhtthhopedupd hmohguvgepshhmthhpohhuthdprhgtphhtthhopehfrhgvvggsshguqdgtuhhrrhgvnhht sehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 8 Sep 2024 11:24:58 -0400 (EDT) Date: Sun, 8 Sep 2024 16:24:57 +0100 From: void To: freebsd-current@freebsd.org Subject: Re: Loader needs to be updated message Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <20240908122425.720c256cbe4a0c6ae77ded0d@dec.sakura.ne.jp> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.79 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; RWL_MAILSPIKE_VERYGOOD(-0.20)[103.168.172.144:from]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.144:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4X1v0X2FWmz4H04 On Sun, Sep 08, 2024 at 09:14:50AM -0600, Warner Losh wrote: >On Sun, Sep 8, 2024, 7:50 AM void wrote: >> Do you think a source upgrade on the server would fix the issue? >Yes. But the warning at this time isn't super urgent for you. It is telling >you of problems in the future. > >related: do you think i'd have avoided the issue if the guest was ufs only? >> > >No. This is a host vs guest crossthreading that's unavoidable. OK thanks for that. I'll try upgrading the server to August stablisation week 04262ed78d23 I look after another vm on Azure. It's at 13.2-p11 right now i'd like to update it to 13.3 It's not zfs-on-root but it does have a zfs disk for data. Do you think this type of issue might be present? my fear is an unbootable system or not being able to access the zfs part. The system is managed with freebsd-update --