From nobody Sun Aug 11 16:29:18 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 4Whjll6sWLz5T9H5 for ; Sun, 11 Aug 2024 16:29:23 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (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-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Whjll0yqcz49YL for ; Sun, 11 Aug 2024 16:29:22 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=diIjWWeI; dmarc=pass (policy=quarantine) header.from=blastwave.org; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 47BGTIWu052216 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Sun, 11 Aug 2024 12:29:19 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1723393760; bh=B6/hG2K12N514B+ewTiJ3Eox+uOVMKttLvLVbXFoRrY=; h=Date:Subject:To:References:From:In-Reply-To; b=diIjWWeI0xWxYByBzlP9rflTaKejGBwgpalA31CvCqLYYtjW0ps2rWj9T0jAEAQlK CXNBygD0qtOCgeTpvGoA1RidOlQPFxofyKGG0dm/JSsAB4ihOq6C1BtWFkpJl5IDvC aU7Err/kRd2PRxa+811NtgJULgUyc88+p7YPseDvKLBrv84LvnyK/XB/kHeTuaDTm1 0kTFJ8559mYnJsUBBzHwdPN5hJ8YvnB+3mp1sfe9pRz/S2Cv75NSiCSeJjrwy+MQzJ W+yic+Jnq+Wsrkr3VL4PQLE56MFZx/QZhQ+OFYCWIHdCoT+7T5RKmBDRXgpV7HOpGx Sx44U2SBrj1mQ== Message-ID: <47f96d89-e1d1-43a8-b456-7b30240d1fad@blastwave.org> Date: Sun, 11 Aug 2024 12:29:18 -0400 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 User-Agent: Mozilla Thunderbird Subject: Re: git: ce4dcb97ca43 - main - zfs: merge openzfs/zfs@9c56b8ec7 Content-Language: en-CA To: freebsd-current@freebsd.org References: <20240811021506.04996DB@slippy.cwsent.com> <54076f5e-cd6d-40d6-b4b7-495cf8e67572@blastwave.org> <20240811134119.91DD57F@slippy.cwsent.com> From: Dennis Clarke Organization: GENUNIX In-Reply-To: <20240811134119.91DD57F@slippy.cwsent.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 47BGTIWu052216 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.69 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx:c]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Whjll0yqcz49YL On 8/11/24 09:41, Cy Schubert wrote: > In message <54076f5e-cd6d-40d6-b4b7-495cf8e67572@blastwave.org>, Dennis > Clarke > writes: >> On 8/10/24 22:15, Cy Schubert wrote: >>> In message , Mark Millard >>> write >>> s: >> >>>> =E2=80=A2 [2:12 PM]Flox: getting this error in ZFS since recent = >>>> update in HEAD >>>> =E2=80=A2 [2:12 PM]Flox: >>>> sysctl_warn_reuse: can't re-use a leaf = >>>> (kstat.zfs.zroot.dataset.objset-0x204.zil_itx_metaslab_slog_alloc)! >>>> pid 58 (zpool) is attempting to use unsafe AIO requests - not logging = >>>> anymore >>>> >>>> =E2=80=A2 [2:13 PM]Flox: >>>> FreeBSD fbsd15.localdomain 15.0-CURRENT FreeBSD 15.0-CURRENT #0 = >>>> main-aea9dba46b: Sat Aug 10 16:48:02 EDT 2024 = >>>> mike@fbsd15.localdomain:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG = >>>> amd64 >>> >>> Yeah. I'm getting tons of these on all my machines as well. >>> >>> sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.cwsys.dataset.objset-0x2c >> c >>> d.zil_itx_metaslab_slog_alloc)! >>> >>> >> >> >> Yep. Seems to be a real thing just pouring out all over the console here >> too : >> >> >> sysctl_warn_reuse: can't re-use a leaf >> (kstat.zfs.t1.dataset.objset-0x4b0.zil_itx_metaslab_slog_alloc)! > > This only happens on import: when the system boots and when any pools are > imported later on. > Sadly .. nope ... that is not the case : triton# uptime 4:27PM up 11:33, 2 users, load averages: 2.76, 0.93, 0.37 triton# triton# sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x639a.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x639a.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x639a.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x6508.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x6508.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x6508.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x5e74.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x5e74.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x5e74.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x6603.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x6603.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x6603.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x5e7c.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x5e7c.zil_itx_metaslab_slog_alloc)! sysctl_warn_reuse: can't re-use a leaf (kstat.zfs.t1.dataset.objset-0x5e7c.zil_itx_metaslab_slog_alloc)! So seems to be a thing when the machine is running and doing things like a poudriere bulk build etc etc .. I have not seen it when the machine is just twiddling its thumbs pondering an existential crisis. Yet. >> >> >> Just a tad uncomfortable to see. > > Uncomfortable but harmless. > In that case let's make it go away .. mmmkay ? -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken