From nobody Thu Nov 28 15:55:51 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 4Xzgs10DS0z5dtv5 for ; Thu, 28 Nov 2024 15:56:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xzgs05KrFz4Mlb; Thu, 28 Nov 2024 15:56:04 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-f171.google.com with SMTP id 38308e7fff4ca-2ff550d37a6so11417981fa.0; Thu, 28 Nov 2024 07:56:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732809363; x=1733414163; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3bWj8X1hGnRwIGLoA2Civ1vke8LiOji56hB224G+PuU=; b=kCCR5KtIt/fIQxSw5mqDGJ47Mi8FyLywL5n55tn0QgwykNs3apINQ/3m7/4Kt9RfkF M5yMQzFGQWaJ3oEUIGArOcieXDsryUs2uO4K36Rf+/kMzbgSiIEOuSyrmhp+H69rirxQ PzPeTXPXoW3r8pGSvdRKlEW8/vZbwYJ55iy2Tov5nCmldMc4LwQmu5SdqXQtOytFdxWi 14+R3jpjzTA8/mC8ma1e+kqQhajIGb06T6FwwcvdIXv6Qn5bUUFa5Y/UzsyeME/PvW4H 3yDsWUrb7ZEWCEI46AYA7pGsDnSbayFF790UN/xMu8PRNszm68o24A1DRvQsjoO7gTQW PV6A== X-Forwarded-Encrypted: i=1; AJvYcCX0bSleXemMxP/7XaGKmCmULR4ZSUr5XQ5QLi7Symh/466BGIvuDfVfONoTXcf0ikFI6Nm7GztGVVCrjaiufBM=@freebsd.org X-Gm-Message-State: AOJu0YyeHaZYNT1NW89BVdF88sZtfIrzI9DE4TbwoXZv0wcYC56pYyoA ID44CPNvc0M/lIyuvNzNZhihUr7DxeDh5hkyA6Q4+/7eOlpaVHYZfK0nONhfXDpq2ZHq3VVW+eq bD6TsxfOrHeYnJsgU5oI/thqnp9TahA== X-Gm-Gg: ASbGnctoUnY/pqFwnaHZSKD409mS/pZ2lDrFlmchVdy70H1+WEwKVhkhdKlyJwy+mLJ mkld3E+PrEkMlN6QPLUhS3VzSNYdEJv9MdDXSIUSW3/A7ZbRj+1oljS5tVV6Evg+v9A== X-Google-Smtp-Source: AGHT+IFR11FDrIAwLZiABntrQD18TWmFjX8Zz3z8DJyD3D41XvlN/TXxjdxEXJlWXtvyFVI1x6npka6HPyn3zIeTxEU= X-Received: by 2002:a05:651c:19a2:b0:2fb:4b40:1e18 with SMTP id 38308e7fff4ca-2ffd605c41cmr41689981fa.13.1732809362568; Thu, 28 Nov 2024 07:56:02 -0800 (PST) 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 References: <5798b0db-bc73-476a-908a-dd1f071bfe43@blastwave.org> <22187e59-b6e9-4f2e-ba9b-f43944d1a37b@blastwave.org> <722a3644-3af6-4ff9-b1ee-022c32872001@blastwave.org> In-Reply-To: <722a3644-3af6-4ff9-b1ee-022c32872001@blastwave.org> From: Alan Somers Date: Thu, 28 Nov 2024 09:55:51 -0600 Message-ID: Subject: Re: zpools no longer exist after boot To: Dennis Clarke Cc: Alan Somers , Current FreeBSD Content-Type: multipart/alternative; boundary="00000000000084ff8b0627fb1e94" 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:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4Xzgs05KrFz4Mlb X-Spamd-Bar: ---- --00000000000084ff8b0627fb1e94 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Nov 28, 2024, 9:47=E2=80=AFAM Dennis Clarke = wrote: > On 11/28/24 09:52, Alan Somers wrote: > > On Thu, Nov 28, 2024, 8:45=E2=80=AFAM Dennis Clarke > wrote: > > > ... > > > > For "zpool import", the "-c" argument instructs zfs which cachefile to > > search for importable pools. "-O", on the other hand, specifies how the > > cachefile property should be set after the pool is imported. > > > > I have to wonder what value there is in NOT having the cachefile > property set in a zpool ? Certainly given that the zpool RC script > really wants to check in a few places and then use those cache files. > > -- > -- > Dennis Clarke > RISC-V/SPARC/PPC/ARM/CISC > UNIX and Linux spoken > Usually the default value for cachefile is sufficient. In fact, the only time I've ever needed to set cachefile has been when I DON'T want the pool to import at boot. I wonder if there was some other reason, since resolved, why your pools didn't import the first time. And subsequently they didn't import because you set the cachefile to a non default value? > --00000000000084ff8b0627fb1e94 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Nov 28, 2024, 9:47=E2=80=AFAM Dennis Clarke <dclarke@blastwave.org> wrote:
=
On 11/28/24 09:52, = Alan Somers wrote:
> On Thu, Nov 28, 2024, 8:45=E2=80=AFAM Dennis Clarke <dclarke@bla= stwave.org> wrote:
>
...
>
> For "zpool import", the "-c" argument instructs zf= s which cachefile to
> search for importable pools. "-O", on the other hand, specif= ies how the
> cachefile property should be set after the pool is imported.
>

I have to wonder what value there is in NOT having the cachefile
property set in a zpool ?=C2=A0 Certainly given that the zpool RC script really wants to check in a few places and then use those cache files.

--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken

Usually the default value for cachefile is sufficient.= In fact, the only time I've ever needed to set cachefile has been when= I DON'T want the pool to import at boot. I wonder if there was some ot= her reason, since resolved, why your pools didn't import the first time= . And subsequently they didn't import because you set the cachefile to = a non default value?
--00000000000084ff8b0627fb1e94--