[OpenIndiana-discuss] ZFS Pool configuration hanging around

[Stephan Budach]

Am 17.01.11 12:30, schrieb Michelle Knight:
> I'm using an external caddy to mount "backup" drives to. The ZFS pools are,
> rather imaginatively, called, "backup."
>
> However, there seems to be a phantom of an old set that was present when the
> machine hung once upon a time, and I can't get rid of it. I've tried deleting
> /etc/zfs/zpool.cache but no joy.
>
> Here you can see the problem. A single drive is on c3d0p0, called "backup." (I
> know, there is no redundancy, I'm testing)
>
> A zpool import shows both the valid drive but also the phantom set.
>
> This means I've got to import the pool via the id number.
>
> mich at jaguar:/etc/zfs# zpool import
>    pool: backup
>      id: 10642222873577100856
>   state: ONLINE
> status: The pool is formatted using an older on-disk version.
> action: The pool can be imported using its name or numeric identifier, though
>          some features will not be available without an explicit 'zpool
> upgrade'.
> config:
>
>          backup      ONLINE
>            c3d0p0    ONLINE
>
>    pool: backup
>      id: 15407100200514227053
>   state: FAULTED
> status: One or more devices are missing from the system.
> action: The pool cannot be imported. Attach the missing
>          devices and try again.
>          The pool may be active on another system, but can be imported using
>          the '-f' flag.
>     see: http://www.sun.com/msg/ZFS-8000-3C
> config:
>
>          backup        FAULTED  corrupted data
>            mirror-0    DEGRADED
>              c2t4d0p0  ONLINE
>              c5t0d0    UNAVAIL  cannot open
>
>
> Anyone know how to get rid of this phantom set from the system please? I've
> tried "destroy" but it obviously can't find the pool to get rid of it.
>
> To make it worse, the drive on c2t4d0p0 was part of the faulted backup set.
>
> Should I reboot after clearing the zpool cache file? Would that be the missing
> step?
>
> I know ... I get myself in to some really dumb situations, don't I.
I'd import the good zpool using it's numeric identifier and then just 
rename it alongside the import like this:

zpool import 10642222873577100856 <newName>

Then export it back out and see what zpool import returns. If it still 
returns the ghost zpool you can of course reboot the host once more and 
see if that clears things up.

Cheers,
budy