From owner-freebsd-current Sat Jul 25 13:52:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26879 for freebsd-current-outgoing; Sat, 25 Jul 1998 13:52:21 -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 NAA26849 for ; Sat, 25 Jul 1998 13:52: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 PAA04137 for ; Sat, 25 Jul 1998 15:51:49 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id PAA02587; Sat, 25 Jul 1998 15:51:49 -0500 (CDT) Message-ID: <19980725155148.43084@mcs.net> Date: Sat, 25 Jul 1998 15:51:48 -0500 From: Karl Denninger To: current@FreeBSD.ORG Subject: MMAP problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, 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 actually happening when it should, and is being thrown away. This shows up as a corrupted batch when you try to transmit to others. I'm working on trying to isolate this, and will have more when I know better what is going on. -- -- 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