dear all, victor,
i am most happy to report that the problems were somehwat hardware-related,
caused by a damaged / dangling SATA cable which apparently caused long delays
(sometimes working, disk on, disk off, ...) during normal zfs operations. Why
the -f produced a kernel panic I'm unsure. In
We have the same problem since of today. The pool was to be "renamed" width
zpool export, after an import it didn't come back online. A import -f results
in a kernel panic.
zpool status -v freports a degraded drive also.
I'll also try to supply som,e traces and logs.
--
This message posted fro
