-
but
I run into this problem on both 2.2.8 and 2.2.7 kernels (actually this includes the zfs-2.2.8 staging branch, but not the rest of 2.2.8) using the 2.2.8 userspace. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
@robn FYI |
Beta Was this translation helpful? Give feedback.
-
That's Fortunately, "destroying" a pool is actually just an export that flips a bit to say "ignore this pool when trying to detect a pool. If that's all true, try If it does import, you should run a scrub as a precaution. I wouldn't expect any issues, but it never hurts. And if you don't know where that destroy came from, probably a good opportunity to look into that! |
Beta Was this translation helpful? Give feedback.
That's
POOL_STATE_DESTROYED
, that is, you ranzpool destroy
. I don't know if that's true, or if some script you use or something else did it, but that looks like a clean, successful destroy.Fortunately, "destroying" a pool is actually just an export that flips a bit to say "ignore this pool when trying to detect a pool.
dbgmsg
suggests a clean and tidy import, and then an exit because of the "destroyed" state.If that's all true, try
zpool import -D
, which is "consider deleted pools". If it shows your pool, and it's not a weird state (failed, imported elsewhere), you can tryzpool import -f -D hydrapool
to import it (which will also clear the "deleted" state). Don't try to …