From owner-freebsd-current@FreeBSD.ORG Thu Feb 19 16:22:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55EF916A4CE; Thu, 19 Feb 2004 16:22:34 -0800 (PST) Received: from new.iagu.net (new.iagu.net [203.32.153.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB75C43D1D; Thu, 19 Feb 2004 16:22:33 -0800 (PST) (envelope-from andrewr@iagu.net) Received: from [203.32.153.125] (pop@ns.iagu.net [203.32.153.69]) by new.iagu.net (8.12.9/8.12.4) with ESMTP id i1K0MVjl070635; Fri, 20 Feb 2004 10:52:31 +1030 (CST) (envelope-from andrewr@iagu.net) Mime-Version: 1.0 X-Sender: andrewr@127.0.0.1 Message-Id: In-Reply-To: <20040218000611.GC64477@wantadilla.lemis.com> References: <20040218000611.GC64477@wantadilla.lemis.com> Date: Fri, 20 Feb 2004 10:52:28 +1030 To: FreeBSD current users From: Andrew Rutherford Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Mailman-Approved-At: Thu, 19 Feb 2004 20:36:12 -0800 cc: Greg 'groggy' Lehey Subject: Re: Soft updates problems with 5.2.1-RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2004 00:22:34 -0000 At 10:36 AM +1030 18/2/04, Greg 'groggy' Lehey wrote: >Based on the fact that this happens when big mail messages are being >received, we've guessed that the file system in question is /var, and >we've turned off soft updates there. We're both out of town >effectively for the rest of the week, and we'll continue looking after >that, but if anybody has any thoughts, we'd be grateful. More information - softupdates was turned off, and the backtraces stopped coming, but nat still stops working when the system is under load. Interestingly, they have a number of nat daemons running (different external IP's for different internal IP ranges), and it seems the nat daemons affected are those that are idle at the time of the system load. For example, in one burst of system load around noon, natd #1 was busy and natd #2 was idle, and the operation of natd #2 failed. Correct operation resumed when /etc/rc.firewall was run again to reload the ipfw rules, while the natd itself was not restarted. In the evening of the same day, natd #1 was idle and natd #2 was busy when a large burst of email (not under NAT) went through the system, and natd #1 was not operating correctly. -- Andrew Rutherford sip:andrewr@iagu.net 244 Pirie Street Iagu Networks tel:+61-8-8425-2255 Adelaide SA 5000 http://www.iagu.net/ mailto:andrewr@iagu.net Australia