On 11/28/24 10:55, Alan Somers wrote:
On Thu, Nov 28, 2024, 9:47 AM Dennis Clarke <dcla...@blastwave.org> wrote:
On 11/28/24 09:52, Alan Somers wrote:
On Thu, Nov 28, 2024, 8:45 AM Dennis Clarke <dcla...@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?
I am at a loss. Really.
Getting the iSCSI stuff working was a real treat and this just makes
things even more strange. I really do not know.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
