I have the same issue as described by Ned in his email. I had a zfs
recv going that deadlocked against a zfs list; after a day of leaving
them hung I finally had to hard reset the box (shutdown wouldn't, since
it couldn't terminate the processes). When it came back up, I wanted to
zfs destroy
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Ariel T. Glenn
I have the same issue as described by Ned in his email. I had a zfs
recv going that deadlocked against a zfs list; after a day of leaving
them hung I finally had to hard
Formerly, if you interrupted a zfs receive, it would leave a clone with a % in
its name, and you could find it via zdb -d and then you could destroy the
clone, and then you could destroy the filesystem you had interrupted receiving.
That was considered a bug, and it was fixed, I think by Sun.
