> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Ian Collins
> On a Solaris 11 (SR3) system I have a zfs destroy process what appears
> to be doing nothing and can't be killed. It has used 5 seconds of CPU
> in a day and a half, but truss -p won't attach. No data appears to have
> been removed. The dataset (but not the pool) is busy.
> I thought this was an old problem that was fixed long ago in Solaris 10
> (I had several temporary patches over the years), but it appears to be
> alive and well.
How big is your dataset? On what type of disks/pool?
zfs destroy does indeed take time (unlike zpool destroy.) A couple of days
might be normal expected behavior, depending on your configuration. You
didn't specify if you have dedup... Dedup will greatly hurt your zfs
destroy speed, too.
That being said, sometimes things go wrong, and I don't have any suggestion
for you to determine if yours is behaving "as expected." Or not.
zfs-discuss mailing list