UPDATE (for those following along at home)...
After patching to latest and greatest Solaris 10 kernel update
and getting firmware on both OS drives (72 GB SAS) and server updated
to latest and greatest, Oracle has now officially declared it a bug
(CR#7082249). No word on when I'll hear
Another update:
The configuration of the zpool is 45 x 1 TB drives in three
vdev's, each of 15 drives. We should have a net capacity of between 30
and 36 TB (and that agrees with my memory of the pool). I ran zdb -e
-d against the pool (not imported) and totaled the size of the
datasets and
Updates to my problem:
1. The destroy operation appears to be restarting from the same point
after the system hangs and has to be rebooted. Oracle gave me the
following to track progress:
echo '::pgrep zpool$ |::walk thread|::findstack -v' | mdb -k | grep
dsl_dataset_destroy
then take first arg
I am having a very odd problem, and so far the folks at Oracle
Support have not provided a working solution, so I am asking the crowd
here while still pursuing it via Oracle Support.
The system is a T2000 running 10U9 with CPU-2010-01and two J4400
loaded with 1 TB SATA drives. There is
An additional data point, when i try to do a zdb -e -d and find the
incomplete zfs recv snapshot I get an error as follows:
# sudo zdb -e -d xxx-yy-01 | grep %
Could not open xxx-yy-01/aaa-bb-01/aaa-bb-01-01/%1309906801, error 16
#
Anyone know what error 16 means from zdb and how this might
