Re: 8.1 livelock/hangup: possible actions
On 2010-Dec-11 18:14:28 +0500, Eugene M. Zheganin e...@norma.perm.ru wrote: I'm having problems with 8.1-REL/zfs/amd64. It's a IMB x3250 m2 system, 1Gb RAM, dualcore intel e3110, two bge(4) and LSI1064e disk controller. 1GB RAM is really light on for ZFS and there are some known ARC issues in 8.1 that can lead to free memory starvation. The most obvious indicator of this issue is that free memory reported by top OR systat -v drops _very_ low although there is plenty of cache and inactive memory. If you can't update to 8-stable, try changing arc_memory_throttle() in /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c to have uint64_t available_memory = ptoa((uintmax_t)cnt.v_free_count + cnt.v_cache_count); instead of uint64_t available_memory = ptoa((uintmax_t)cnt.v_free_count); at the top of the function. This fixes the worst bug but there are lots of other fixes if you upgrade. -- Peter Jeremy pgpMi5QjNUH8u.pgp Description: PGP signature
8.1 livelock/hangup: possible actions
Hi. I'm having problems with 8.1-REL/zfs/amd64. It's a IMB x3250 m2 system, 1Gb RAM, dualcore intel e3110, two bge(4) and LSI1064e disk controller. Suddenly it can stop answering to network requests and nothing works except of the keyborad, so I guess the system isn't really dead. No trap screen, no reboot. I realize very clearly that this description isn't useful in any way. :) So I'm asking what can I do to localize the source of the problem or get additional diagnostics ? Only reset button currently comes to my mind, it helps of course, but it doesn't provide me with any information about what is happening. After reboot logs are empty for the period of the hangup. Thanks. Eugene. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.1 livelock/hangup: possible actions
on 11/12/2010 15:14 Eugene M. Zheganin said the following: Hi. I'm having problems with 8.1-REL/zfs/amd64. It's a IMB x3250 m2 system, 1Gb RAM, dualcore intel e3110, two bge(4) and LSI1064e disk controller. Suddenly it can stop answering to network requests and nothing works except of the keyborad, so I guess the system isn't really dead. Can you enter debugger via its key combination? No trap screen, no reboot. I realize very clearly that this description isn't useful in any way. :) So I'm asking what can I do to localize the source of the problem or get additional diagnostics ? Only reset button currently comes to my mind, it helps of course, but it doesn't provide me with any information about what is happening. After reboot logs are empty for the period of the hangup. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
