Re: zfs forgetting cache wedges?

[mlelstv%serpens.de@localhost (Michael van Elst)]

kardel%netbsd.org@localhost (Frank Kardel) writes:

>After a boot it looks like this:
>NAME                   SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP 
>  HEALTH  ALTROOT
>pool-1                8.94T  2.76T  6.17T         -     5%    30%  1.11x 
>  ONLINE  -
>   raidz1              8.94T  2.76T  6.17T         -     5%    30%
>     wedges/zfs10g0-0      -      -      -         -      -      -
>     wedges/zfs10g1-0      -      -      -         -      -      -
>     wedges/zfs10g2-0      -      -      -         -      -      -
>cache                     -      -      -         -      -      -
>   384839849488            -      -      -         -      -      -

>The cache wedge does not look very usable in that state.


Didn't happen here (with recent -current). The device paths for
the pool devices are stored in /etc/zfs/zfs.cache and the device
path to the cache device is stored on the pool devices.

But your pool devices also do not return data, and that's probably
the reason for the strange cache device path that couldn't be read.

NAME              SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
mypool             80M   104K  79.9M         -     4%     0%  1.00x  ONLINE  -
  wedges/image0    80M   104K  79.9M         -     4%     0%
cache                -      -      -         -      -      -
  wedges/image1  95.2M     1K  95.2M         -     0%     0%

-- 
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."