From owner-freebsd-stable Wed Jun 9 10:28:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (nat192.211.mpoweredpc.net [142.177.192.211]) by hub.freebsd.org (Postfix) with ESMTP id F3E0F14D23; Wed, 9 Jun 1999 10:28:46 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id OAA95797; Wed, 9 Jun 1999 14:28:51 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 9 Jun 1999 14:28:51 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: MMAP() in STABLE/CURRENT ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Over the past week and a bit, the INN -CURRENT source tree had a major upheaval of code, in order to fix the major problem where reader speed sucked. What used to take >1min to load up a newsgruop now generally takes mere seconds (no exaggeration, try it)... The problem is that the new code makes *heavy* use of MMAP() ... When the code was put in place, I immediately upgraded my server to give the code a good test (am one of the developers over there) in a production environment, and ever since then, my system locks up around 24hrs uptime, requiring a cold boot. I cannot get into DDB, since I'm over a serial console, so debugging this has proved to be next to impossible :( After discussing this with a few other FreeBSD'rs who have seen similar problems, the point got brought up that it was believed there was still a problem with our MMAP() implementation ... basically where it could still cause a race condition to be generated ... Since this problem is crucial to the stability of my server, as well as anyone that keeps up on INN, I'm curious as to whether or not there are any known problems with MMAP(), and, if so...what can I do to help rectify the problem? I run CURRENT at home and STABLE in production, but the production server is the only one that I believe has enough load on her to be able to trigger it... Is this a problem that is fixed in CURRENT, but hasn't migrated down into STABLE? Is there any way of adding some sort of debug code to STABLE such that if the race condition is trigger, it will at least pop up a message onto the console letting me know its happened so that I know its MMAP() related? Thanks... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message