Date: Thu, 28 Nov 2024 09:55:51 -0600 From: Alan Somers <asomers@freebsd.org> To: Dennis Clarke <dclarke@blastwave.org> Cc: Alan Somers <asomers@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: zpools no longer exist after boot Message-ID: <CAOtMX2i1dFXdyTXK-18cs48uJi2u6LwTDDz8kMPdpEXQbzg7dA@mail.gmail.com> In-Reply-To: <722a3644-3af6-4ff9-b1ee-022c32872001@blastwave.org> References: <5798b0db-bc73-476a-908a-dd1f071bfe43@blastwave.org> <CAOtMX2hKCYrx92SBLQOtekKiBWMgBy_n93ZGQ_NVLq=6puRhOg@mail.gmail.com> <22187e59-b6e9-4f2e-ba9b-f43944d1a37b@blastwave.org> <CAOtMX2gdGWRfOa%2Bm9FctMNCVwDQ9GUE=vhxaEY_gorDFOU0fHg@mail.gmail.com> <722a3644-3af6-4ff9-b1ee-022c32872001@blastwave.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Thu, Nov 28, 2024, 9:47 AM Dennis Clarke <dclarke@blastwave.org> wrote: > On 11/28/24 09:52, Alan Somers wrote: > > On Thu, Nov 28, 2024, 8:45 AM Dennis Clarke <dclarke@blastwave.org> > 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? > [-- Attachment #2 --] <div dir="auto"><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 28, 2024, 9:47 AM Dennis Clarke <<a href="mailto:dclarke@blastwave.org">dclarke@blastwave.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 11/28/24 09:52, Alan Somers wrote:<br> > On Thu, Nov 28, 2024, 8:45 AM Dennis Clarke <<a href="mailto:dclarke@blastwave.org" target="_blank" rel="noreferrer">dclarke@blastwave.org</a>> wrote:<br> > <br> ...<br> > <br> > For "zpool import", the "-c" argument instructs zfs which cachefile to<br> > search for importable pools. "-O", on the other hand, specifies how the<br> > cachefile property should be set after the pool is imported.<br> > <br> <br> I have to wonder what value there is in NOT having the cachefile<br> property set in a zpool ? Certainly given that the zpool RC script<br> really wants to check in a few places and then use those cache files.<br> <br> -- <br> --<br> Dennis Clarke<br> RISC-V/SPARC/PPC/ARM/CISC<br> UNIX and Linux spoken<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">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?</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> </blockquote></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2i1dFXdyTXK-18cs48uJi2u6LwTDDz8kMPdpEXQbzg7dA>