Sorry, I did not hit this type of error...
AFAIK the pool writes during zfs receive are done by current code (i.e. ZFSv22
for you) based on data read from the backup stream. So unless there are
corruptions on the pool which happened to be at the same time as you did your
restore, this procedure should not have broken your pool. It was just a
(special) write by your OS version's code, nearly same as any other.
Did you have any hardware problems at that time, like brown-outs, overheating,
occasional push of a reset button?
Maybe some experts here would be able to comment better or guide you through
troubleshooting and collecting data, if you post your OS version details, error
messages especially, etc.
For example, if for some reason your hostid changed (i.e. you used the safe
mode miniroot) and the pool tank was not exported afterwards, the error may be
like "Pool is busy or used by another system" with a solution as simple as that
you'd have to do a forced import ("zpool import -f tank") - if it is indeed a
local non-networked pool and no other machine really uses it.
HTH,
//Jim
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
