Hmmm, this looks like a bug to me. The single argument form of 'zpool
replace' should do the trick. What has happened is that there is enough
information on the disk to identify it as belonging to 'tank', yet not
enough good data for it to be opened. Incidentally, you you send me the
contents of
I have a raidz pool which looks like this after a disk failure:
# zpool status
pool: tank
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
a