setup volume vol2 import = kernel panic BOOM!
I have a volume that was setup as a mirror, one of the disks took a dump and was replaced, the volume wouldn't show up in nexenta, but I can do setup volume vol2 clear-errors and it comes back online. The next issue is that I can do zfs list and see the folder I create /vol2/vm but I can access it. If I try and do anything with the actual vol2/vm folder it kernel panics and dies a fiery death. Is my data lost?
Few actions i would suggest:
1) wait for 3.0.3 where some more kernel bug fixes will be added. Specifically - auto rollback on ZFS pool import.
2) try to export ZFS pool then and import it again.
3) move ZFS pool version to the latest by using upgrade-version command
If this still doesn't work, send/recv it to the new pool and see if new meta-data formed behaves any better