From owner-freebsd-hackers  Sun Mar 31 07:07:39 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA27386
          for hackers-outgoing; Sun, 31 Mar 1996 07:07:39 -0800 (PST)
Received: from asstdc.scgt.oz.au (asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA27376
          for <hackers@freebsd.org>; Sun, 31 Mar 1996 07:07:25 -0800 (PST)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.5/BSD4.4) id BAA21645
          Mon, 1 Apr 1996 01:06:22 +1000 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199603311506.BAA21645@asstdc.scgt.oz.au>
Subject: Re: "active" (INND14unoff4,shared) gets corrupted
To: rashid@rk.ios.com (Rashid  Karimov)
Date: Mon, 1 Apr 1996 01:06:21 -3800 (EST)
Cc: hackers@freebsd.org
In-Reply-To: <199603311416.JAA15590@rk.ios.com> from "Rashid  Karimov" at Mar 31, 96 09:16:40 am
X-Mailer: ELM [version 2.4 PL24beta]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Rashid  Karimov writes:

> I have INND1.4seunoff4 installed on 3 computers here - 
> 2 P6-200 and one P-166, all under FreeBSD 2.1-Release.
> In one case(P-166) I use shared active patch and ccd driver
> to max the HDs perf.

Disable MMAP .. it doesn't work in 2.1-R and I have my doubts if it works
in either -stable or -current. This _will_ corrupt your active file.

I had no success with the shared-active patch with -stable .. occasionally a
reader (nnrpd) will just sit there and chew ~100% of the available CPU. The
same goes for the "robustness" patch for innxmit .. don't use it either. It
displays very similar symptoms if the network connection is broken in an
untimely fashion.

I haven't had the time to check why both of these patches do simialr things
but I suspect a rapid select call loop :-(

	michael