From owner-freebsd-current Sun Jul 26 18:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10737 for freebsd-current-outgoing; Sun, 26 Jul 1998 18:03:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10716 for ; Sun, 26 Jul 1998 18:03:43 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id SAA09631; Sun, 26 Jul 1998 18:03:13 -0700 (PDT) Date: Sun, 26 Jul 1998 18:03:13 -0700 (PDT) From: Matthew Dillon Message-Id: <199807270103.SAA09631@apollo.backplane.com> To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: Diablo corruption on the filesystem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I turned off USE_PCOMMIT_SHM, USE_PCOMMIT_RW_MAP, USE_KP_RW_MAP and :DO_COMMIT_POSTCACHE and recompiled diablo (but did NOT reinstall dnewslink, :if that matters). I assume you mean DO_PCOMMIT_POSTCACHE here, not DO_COMMIT_POSTCACHE. :Something significant happend when I changed the behavior of diablo :internally. : :Does this shed any light on the issue? What have I actually done in terms :of the calls made to the mmap routines by disabling these options? Hmmm. If DO_PCOMMIT_POSTCACHE is turned off the stress on the history file will increase, but that's about it. It could also have a slight serialization effect on multiple feeders that are nearly-in-sync due to history file locking. *PCOMMIT_SHM & RW_MAP should not have any effect at all. -Matt :-- :-- :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 : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message