zpool destroy causes panic
Dan Langille
dan at langille.org
Sun Jul 25 20:41:09 UTC 2010
On 7/25/2010 4:37 PM, Volodymyr Kostyrko wrote:
> 25.07.2010 23:18, Jeremy Chadwick wrote:
>> Footnote: can someone explain to me how ZFS would, upon reboot, know
>> that /tmp/sparsefile[12].img are part of the pool? How would ZFS taste
>> metadata in this situation?
>
> Just hacking it.
>
> Each ZFS device which is part of the pool tracks all other devices which
> are part of the pool with their sizes, device ids, last known points. It
> doesn't know that /tmp/sparsefile[12].img is part of the pool, yet it
> does know that pool have had some /tmp/sparsefile[12].img before and now
> they can't be found or current contents doesn't look like ZFS device.
>
> Can you try moving current files to /tmp/sparsefile[34].img and then
> readd them to the pool with zpool replace? One by one please.
I do not know what the above paragraph means.
--
Dan Langille - http://langille.org/
More information about the freebsd-stable
mailing list