Interesting, I had assumed the cause of my problem was de-dup because the symptoms are similar to what others have reported destroying their deduped datasets, but their system hangs didn't happen for hours while my system hard locks in 3 to 4 minutes. But now you have me thinking because the dataset I was using was also a zvol shared out through ISCSI (via comstar though) and it was deduped as well.
Although, my system hung during the destroy which more closely matched the symptoms from the threads dealing with destroying a deduped zfs dataset and making the pool non-importable threads. Did your destroy happen to hangup mid-way through? zpool destroy would have just given you some funky error like non-existent poolname or something. so you probably used zfs destroy correctly. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
