Ah ha. Interesting procedure and bug report. This is starting to make sense.
Another interesting bug report:
6416757 zfs could still use less memory
This one is more or less the same thing I have noticed.
I guess I'll add some swap for the short term. :-(
--joe
Roch wrote:
I just ran:
[EMAIL PROTECTED](129): mkfile 5000M f3
Could not set length of f3: No space left on device
Which fails in anon_resvmem:
dtrace -n fbt::anon_resvmem:return/arg1==0/[EMAIL PROTECTED](20)]=count()}
tmpfs`tmp_resv+0x50
tmpfs`wrtmp+0x28c
tmpfs`tmp_write+0x50
genunix`fop_write+0x20
genunix`write+0x270
unix`syscall_trap32+0xcc
1
Which could then be:
4034947 anon_swap_adjust(), anon_resvmem() should call kmem_reap() if availrmem
is low.
FixedInBuild: snv_42
But it is a best practise to run ZFS with some
swap, I actually don't know exactly why, but
possibly to account for such bugs as this one.
-r
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
