From nobody Thu Nov 28 14:16: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 4Xzdfl6vTyz5dmp0 for ; Thu, 28 Nov 2024 14:17:03 +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 "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xzdfl6MB2z40pK for ; Thu, 28 Nov 2024 14:17:03 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; none 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 4ASEGw0U028023 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT); Thu, 28 Nov 2024 09:16:59 -0500 (EST) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1732803419; bh=6YksORMobAmf2if8VHo6jVlEQY/fgNs0R5j8rlYD5Uo=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=CSegFLM8cMRoKzk47/zS9C1BaRQkSG0PtEFkoKa8A4+kDn3Ur5BAH5Q2p+4wUdz/O fsUc2lkINC6h3ZZOSM+7wZJy1g2tv5eBSUqLOXrv9k7VuN4IU2kTFZ7xASIaWtORg6 styXh2OTCaI1w1kNj/wMXhgw2DsFvucvJGB9h650Snilqy7UOP+yHBKFvVmXokQSNf vQxyVY5BKIlYylGan4FmhagE09jzGUUHOgdppiPl52IhgwHh1MEY3DOxEC7q/KHkvu T/SfacAoX+nKIpqAshuykEyM2M6YASItirPza6avUa8aHCNIICHVNdN5Vcl5xUtdb7 Vy8tmO9LvjOQg== Message-ID: <043aee93-3dbd-4e6f-b0ee-fc6ebae9b8ef@blastwave.org> Date: Thu, 28 Nov 2024 09:16:57 -0500 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: zpools no longer exist after boot Content-Language: en-CA To: Ronald Klop Cc: Current FreeBSD References: <1764191396.6959.1732802309600@localhost> From: Dennis Clarke Organization: GENUNIX In-Reply-To: <1764191396.6959.1732802309600@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 4ASEGw0U028023 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA] X-Rspamd-Queue-Id: 4Xzdfl6MB2z40pK X-Spamd-Bar: ---- On 11/28/24 08:58, Ronald Klop wrote: > Btw: > > The /etc/rc.d/zpool script looks into these cachefiles: > > for cachefile in /etc/zfs/zpool.cache /boot/zfs/zpool.cache; do > > I didn’t check where the cachefile pool property is used. > Hope this helps resolving the issue. Or maybe helps you to provide more > information about your setup. Ah ha ! So the cachefile property needs to be a specific filename or that script will have no clue. Take a look : titan# zpool get cachefile leaf proteus t0 NAME PROPERTY VALUE SOURCE leaf cachefile - default proteus cachefile - default t0 cachefile - default titan# Those files exist and they seem to be either from early this year or today : titan# ls -l /etc/zfs/zpool.cache /boot/zfs/zpool.cache -rw-r--r-- 1 root wheel 1424 Jan 16 2024 /boot/zfs/zpool.cache -rw-r--r-- 1 root wheel 4960 Nov 28 13:03 /etc/zfs/zpool.cache titan# titan# date -u Thu Nov 28 14:13:51 UTC 2024 titan# titan# uptime 2:13PM up 2:19, 1 user, load averages: 0.00, 0.00, 0.00 titan# titan# zpool set cachefile="/etc/zfs/zpool.cache" leaf titan# zpool set cachefile="/etc/zfs/zpool.cache" proteus titan# zpool set cachefile="/etc/zfs/zpool.cache" t0 However that will not work : titan# zpool get cachefile leaf proteus t0 NAME PROPERTY VALUE SOURCE leaf cachefile - default proteus cachefile - default t0 cachefile - default Let me try just one pool : titan# zpool get cachefile leaf NAME PROPERTY VALUE SOURCE leaf cachefile - default titan# zpool set cachefile="/etc/zfs/zpool.cache" leaf titan# zpool get cachefile leaf NAME PROPERTY VALUE SOURCE leaf cachefile - default titan# So this is even worse. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken