Victor,
The zpool import succeeded on the next attempt following the crash that I
reported to you by private e-mail!
For completeness, this is the final status of the pool:
pool: tank
state: ONLINE
scan: resilvered 1.50K in 165h28m with 0 errors on Sat Jul 3 08:02:30 2010
config:
NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
c0t0d0 ONLINE 0 0 0
c0t1d0 ONLINE 0 0 0
c0t2d0 ONLINE 0 0 0
c0t3d0 ONLINE 0 0 0
c0t4d0 ONLINE 0 0 0
c0t5d0 ONLINE 0 0 0
c0t6d0 ONLINE 0 0 0
c0t7d0 ONLINE 0 0 0
cache
c2t0d0 ONLINE 0 0 0
errors: No known data errors
Thank you very much for your help. We did not need to add additional RAM to
solve this, in the end. Instead, we needed to persist with the import through
several panics to finally work our way through the large inconsistent dataset;
it is unclear whether the resilvering caused additional processing delay.
Unfortunately, the delay made much of the data quite stale, now that it's been
recovered.
It does seem that zfs would benefit tremendously from a better (quicker and
more intuitive?) set of recovery tools, that are available to a wider range of
users. It's really a shame, because the features and functionality in zfs are
otherwise absolutely second to none.
/Andrew[i][/i][i][/i][i][/i][i][/i][i][/i]
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
