From nobody Fri Dec 29 11:03:02 2023 X-Original-To: freebsd-ports@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 4T1jCY1TY5z55sNv for ; Fri, 29 Dec 2023 11:03:05 +0000 (UTC) (envelope-from yuri@FreeBSD.org) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4T1jCX3Cm4z3JKQ for ; Fri, 29 Dec 2023 11:03:04 +0000 (UTC) (envelope-from yuri@FreeBSD.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 198.144.192.42 is neither permitted nor denied by domain of yuri@FreeBSD.org) smtp.mailfrom=yuri@FreeBSD.org; dmarc=none Received: from [192.168.5.3] (c-24-6-36-155.hsd1.ca.comcast.net [24.6.36.155]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id 3BTB334L049054 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 29 Dec 2023 03:03:03 -0800 (PST) (envelope-from yuri@FreeBSD.org) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-36-155.hsd1.ca.comcast.net [24.6.36.155] claimed to be [192.168.5.3] Message-ID: <662cb885-8d45-48c0-9a30-87958951517a@FreeBSD.org> Date: Fri, 29 Dec 2023 03:03:02 -0800 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Is the ZPOOL option broken in poudriere? To: ports References: Content-Language: en-US From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [1.61 / 15.00]; VIOLATED_DIRECT_SPF(3.50)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; XM_UA_NO_VERSION(0.01)[]; DMARC_NA(0.00)[freebsd.org]; FREEFALL_USER(0.00)[yuri]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@FreeBSD.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; R_SPF_SOFTFAIL(0.00)[~all:c]; HAS_XAW(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:7961, ipnet:198.144.192.0/23, country:US]; R_DKIM_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+]; GREYLIST(0.00)[pass,meta] X-Rspamd-Queue-Id: 4T1jCX3Cm4z3JKQ X-Spamd-Bar: + I think I figured this out. The ZPOOL variable was changed several times in the past. Poudriere operates by creating ZFS datasets. These datasets are mounted at different points under /usr/local/poudriere, and such mounts are persistent, and re-created during ZFS initialization. When ZPOOL is changed, the old datasets become invalid and should be removed. The question is: who should remove them? The current answer appears to be: nobody removes them. poudriere just reuses the invalid datasets that are mounted on the ZFS pools that aren't currently configured to use poudriere. So I think that some sort of confusion related to the invalid datasets caused the original issue for me. The problem is gone once I deleted all poudriere-related datasets by hand. Yuri