Kyle McDonald wrote: > J?rgen Keil wrote: > >> > >> Is there some way to get more insight into what is going on here? > > You can try to boot the installer under kmdb control > I suspect this is something ZFS specific, since it doesn't hang when I choose > UFS root. > So if there are more ZFS specifc kmdb commands you'd like run, please let me > know.
In the ::arc output we see that zfs did already shrink the cache to it's minimum size of 64MB; it's in "arc_no_grow" mode; and "memory_throttle_count" is also non zero. So it seems something is using lots of kernel heap memory, and zfs's arc cache tried to adapt to this situation. The ::kmastat output shows no failed memory allocations yet. But some of the kmem caches use *lots* of memory: [4]> ::kmastat cache buf buf buf memory alloc alloc name size in use total in use succeed fail ------------------------- ------ ------ ------ ---------- --------- ----- ... kmem_va_4096 4096 54812 54848 224657408B 66351 0 ... kmem_io_64G_4096 4096 67584 67586 276832256B 337888 0 ... rootnex_dmahdl 1272 86771 86862 118595584B 400380 0 ... These three consume 214MB / 264MB and 113MB. I'm not sure if that is ok, of if there is some kind of leak here. 86000 handles for dma transfer appears to be excessive... Note that the installer is running the 32-bit Solaris kernel, and this has a kernel heap limit of something like 500 - 600MB (IIRC). What kind of disk controllers are you using? What kind of network interfaces? This message posted from opensolaris.org
