>> Правда, не похоже на унылый fsck традиционных ФС? ;)
> Да уж. Унылый fsck по задумке еще и репайрит порушенные метаданные до
> более-менее моунтабельного состояния. Чтобы структуры (то что от них уцелело) разбирал
> бы все-таки драйвер ФС а не юзверь с хексэдитором. Потому что
> второй вариант "немного" сложнее и медленнее. А у вас я такой
> задумки не вижу.Увидь: http://compute.cnr.berkeley.edu/cgi-bin/man-cgi?zpool+1
---
zpool import -F poolname
-F
Recovery mode for a non-importable pool. Attempt to
return the pool to an importable state by discarding
the last few transactions. Not all damaged pools can
be recovered by using this option. If successful,
the data from the discarded transactions is irre-
trievably lost. This option is ignored if the pool
is importable or already imported.
Example 15 Recovering a Faulted ZFS Pool
If a pool is faulted but recoverable, a message indicating
this state is provided by zpool status if the pool was
cached (see cachefile above), or as part of the error output
from a failed zpool import of the pool.
Recover a cached pool with the zpool clear command:
# zpool clear -F data
Pool data returned to its state as of Tue Sep 08 13:23:35 2009.
Discarded approximately 29 seconds of transactions.
If the pool configuration was not cached, use zpool import
with the recovery mode flag:
# zpool import -F data
Pool data returned to its state as of Tue Sep 08 13:23:35 2009.
Discarded approximately 29 seconds of transactions.
---