I am having the exact same problem after destroying a dataset with a few gigabytes of data and dedup. I type zfs destroy vault/virtualmachines which was a zvol with dedup turned on and the server hung, couldn't ping, couldn't get on the console. Next bootup same thing just hangs when importing the filesystems. I removed one of the pool disks and also all the mirrors so that I can experiment without losing the original data. But all of my behaviors are acting the exact same way as in this thread, although I can't lose this particular data as it's been a week since last backup so I am freaking out a little. I am on build 130 and was going to do another backup but was troubleshooting a different issue regarding poor iscsi performance before I did the backup. I deleted that zvol with dedup on and now I'm in the same boat as the parent. same hangs. and interesting thing that happens is that when I hit the power button which usually tells the system to start a shutdown, dur ing these hangs it says not enough kernel memory.
Perhaps a memory leak during the failed destroy is causing the hangups. But literally every description and in here matches my symptoms and during an import I can see the disks get hit pretty hard for a about 3 minutes and then stop cold turkey and the system is unresponsive, just a blinking cursor at the console and I can hit enter to generate a newline but everything is blank. so the console is locked pretty hard. The pool is made up of 3 mirrored vdevs, a cache and a log device. everything was running great until I destroy that one little deduped zvol. I was able to destroy other zvols right before that one. Has anybody had a chance to look at the dump the poster sent up? Thanks -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
