Le 20/10/15 17:36, Richard PALO a écrit : > Le 20/10/15 06:23, Robert Mustacchi a écrit : >> To phrase this more practically, this means that some I/O that was >> issued was not returned. This could be because of a hardware or software >> bug. Figuring out what issued I/Os it was and to what device would be a >> useful next step to make forward progress here. I would start looking at >> the outstanding zio's in mdb with, IIRC something like ::walk zio | >> ::zio -r. >> >> Robert > > Okay, thanks.. I'm trying to make room to expand my dump correctly. > > nothing from my 32G of RAM are available any longer, the kernel taking over > 50%. > attached is gzip'd screenlog with a ::memstat and a ::kmastat from 'mdb -k' >
Okay, I have over 11K lines of output, with very few having a "WAITER"... attached gzip'd output of that plus the memstats, kmastats and even findleaks. Not sure if the failures on: > kmem_firewall_va 641064960B 641064960B 641064960B 1154941 0 > kmem_firewall 374579200B 374579200B 374579200B 1154750 17 > kmem_oversize 266457676B 266481664B 266481664B 174 0 > are normal, though. perhaps the cache was exhausted.. swimming in bits, here. same number here: > kmem_alloc_4096 4096 11952 11952 48955392B 297706 17 I must say that I don't see any particular device errors in my logs either. -- Richard PALO ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
mem.txt.gz
Description: application/gzip
zio.txt.gz
Description: application/gzip
