Matthew Ahrens wrote:
Miroslav Pendev wrote:
I did some more testing, here is what I found:
- I can destroy older and newer snapshots, just not that particular
snapshot
- I added some more memory total 1GB, now after I start the destroy
command, ~500MB RAM are taken right away, there is still ~200MB or so
left.
o The machine is responsive,
o If I run 'zfs list' it shows the snapshot as destroyed (it is gone
from the list).
o There is some zfs activity for about 20 seconds - I can see the
lights of the HDDs of the pool blinking, then it stops
Can you take a crash dump when the system is "hung" (ie. after there is
no more disk activity), and make it available to me?
Miro supplied the dump which I examined and filed bug 6542681. The root
cause is that the machine is out of memory (in this case, kernel virtual
address space).
As a workaround, you can change kernelbase to allow the kernel to use
more virtual address space.
--matt
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
