On Jun 4, 2010, at 10:18 PM, Miles Nordin wrote: >>>>>> "sl" == Sigbjørn Lie <sigbj...@nixtra.com> writes: > > sl> Excellent! I wish I would have known about these features when > sl> I was attempting to recover my pool using 2009.06/snv111. > > the OP tried the -F feature. It doesn't work after you've lost zpool.cache:
Starting from build 128 option -F is documented option for 'zpool import' and 'zpool clear' and it has nothing to do with zpool.cache. Old -F has been renamed to -V In some cases it may be possible to extract configuration details from the in-pool copy of configuration by running zdb -eC <poolname> regards victor > > op> I was setting up a new systen (osol 2009.06 and updating to > op> the lastest version of osol/dev - snv_134 - with > op> deduplication) and then I tried to import my backup zpool, but > op> it does not work. > > op> # zpool import -f tank1 > op> cannot import 'tank1': one or more devices is currently unavailable > op> Destroy and re-create the pool from a backup source > > op> Any other option (-F, -X, -V, -D) and any combination of them > op> doesn't helps too. > > I have been in here repeatedly warning about this incompleteness of > the feature while fanbois keep saying ``we have slog recovery so don't > worry.'' > > R., please let us know if the 'zdb -e -bcsvL <zpool-name>' incantation > Sigbjorn suggested ends up working for you or not. > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss