From nobody Tue Apr 12 22:35:08 2022 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 EAC5C1AF2993 for ; Tue, 12 Apr 2022 22:35:21 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.oetec.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KdLCF1tTSz3LBf for ; Tue, 12 Apr 2022 22:35:21 +0000 (UTC) (envelope-from dclarke@blastwave.org) X-Spam-Status: No X-oetec-MailScanner-From: dclarke@blastwave.org X-oetec-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.731, required 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, DKIM_VALID_EF -0.10, NICE_REPLY_A -1.62, T_SCC_BODY_TEXT_LINE -0.01, URIBL_BLOCKED 0.00) X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-ID: 23CMZ81m016882 X-oetec-MailScanner-Information: Please contact oetec for more information Received: from [10.14.0.14] (static-198-54-132-57.cust.tzulo.com [198.54.132.57]) (authenticated bits=0) by mail.oetec.com (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 23CMZ81m016882 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Tue, 12 Apr 2022 18:35:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=blastwave.org; s=default; t=1649802910; bh=eQQIV+xMoOyi9t+/4FqowQ/DbJwmkvcEMzSs3QDog/4=; h=Date:Subject:To:References:From:In-Reply-To:From; b=K0uwLz2/wGsQtJJdI2FenzDwW2d87iFjEt/w3s2K5L9xc9HF+SKHdUF5C9DTZ10R3 FjxdRrJSrIVg9e9Rgu7XXmgOkdUteL57HcoXpLjZ6cgAwQEnofMaV2a64O8rz6fCsy 4QV9MzBNExxAzjDLRhGNgeRNC2HBqFuv5b3WLv82fmvgQWuL2p/UOxC2j5AR6YH9MJ u8LBYY1+g95RtuFqi0fvJ03uY960sPzngLjzPTL3Uet+vLFvPIq/ChBnPC/bhcA9AA 2rqZT0APYJCQH3/kb3sefit08wbLZnxPsB7So9jil4xyu4O98oSvjarqL1iTWfs2TI a0/ijGHTul1Tw== Message-ID: <093ec3cb-32a1-e316-a369-3a9e8559248a@blastwave.org> Date: Tue, 12 Apr 2022 18:35:08 -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/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: main-n254654-d4e8207317c results in "no pools available to import" Content-Language: en-US To: freebsd-current@freebsd.org References: From: Dennis Clarke In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4KdLCF1tTSz3LBf X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b="K0uwLz2/"; 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 X-Spamd-Result: default: False [-4.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; DKIM_TRACE(0.00)[blastwave.org:+]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-current]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 4/12/22 18:15, Mark Millard wrote: > From: Thomas Laus > Date: Tue, 12 Apr 2022 15:48:32 +0000 : > >> On 4/12/22 08:29, Ronald Klop wrote: >>> Are you guys both using NVME or EFI? Just wondering if the common >>> problem is in ZFS or some other component. >>> I will try to gather more information on the machine that actually demonstrates the problem in question. >> I just repeated this issue on the desktop computer that is used for my >> weekly builds that get distributed to the other PC's in the house. Excellent isolation test. I tried the same sort of process on a separate machine to no avail. I was not using NVME storage. I was using a brand new Samsung SSD and you can see that listed in the output : https://lists.freebsd.org/archives/freebsd-current/2022-April/001759.html * * * * the above should be considered a red herring * * * * That machine simply worked as expected. Slight surprise but then again no one else was seeing this issue. Until Thomas Laus also caught it : https://lists.freebsd.org/archives/freebsd-current/2022-April/001761.html So we have at least two examples in the wild. I will focus on the problem case I have and try to get better information. Somehow. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional