From owner-freebsd-current Mon Jul 27 08:05:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01011 for freebsd-current-outgoing; Mon, 27 Jul 1998 08:05:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00997 for ; Mon, 27 Jul 1998 08:05:14 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id KAA01450; Mon, 27 Jul 1998 10:04:47 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id KAA24543; Mon, 27 Jul 1998 10:04:46 -0500 (CDT) Message-ID: <19980727100446.04271@mcs.net> Date: Mon, 27 Jul 1998 10:04:46 -0500 From: Karl Denninger To: dmlb@ragnet.demon.co.uk Cc: current@FreeBSD.ORG, Pierre Beyssac Subject: Re: MMAP problems References: <19980725155148.43084@mcs.net>; <19980727152658.A24276@mars.hsc.fr> <199807271501.IAA28873@mailgate.cadence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807271501.IAA28873@mailgate.cadence.com>; from Duncan Barclay on Mon, Jul 27, 1998 at 04:00:55PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 27, 1998 at 04:00:55PM +0000, Duncan Barclay wrote: > > On Sat, Jul 25, 1998 at 03:51:48PM -0500, Karl Denninger wrote: > > > I believe I have found a rather serious MMAP problem in -CURRENT. > > > > > > Diablo (the news system) is the test case; with MMAP enabled it will randomly > > > write exactly one block (512 bytes) of zeros into the article spool files > > > rather than the proper data - its almost like an update via MMAP isn't > > > > I have seen an extremely similar problem, both on 2.2.6 and > > -current, with INN 2.0 configured to use MMAP for the active file. > > It is fairly easy to reproduce by doing a "ctlinnd newgroup". After > > that, a bunch of zeroes appears in the active file. > > > > I haven't bothered investigating the problem for lack of time > > because configuring INN to use read() just works and because I > > wasn't sure it was a FreeBSD problem, but I'm ready to do any > > testing I can to help fix this. > > -- > > Ditto same problem with inn on -2.2.5, and inn 1.5.2. > I seem to remember that this was documented in the inn instructions? > > Duncan Sigh.... This one is pretty important folks; we need to get some attention focused on this since it appears to cut across all the various releases out there right now. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message