From owner-freebsd-stable Tue Aug 24 13:35: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from erlenstar.demon.co.uk (erlenstar.demon.co.uk [194.222.144.22]) by hub.freebsd.org (Postfix) with ESMTP id 6F96515125 for ; Tue, 24 Aug 1999 13:34:54 -0700 (PDT) (envelope-from andrew@erlenstar.demon.co.uk) Received: (from andrew@localhost) by erlenstar.demon.co.uk (8.8.8/8.8.8) id VAA10850; Tue, 24 Aug 1999 21:34:40 +0100 (BST) (envelope-from andrew) To: freebsd-stable@freebsd.org Subject: Re: INNd sticks in "vmopar" state References: From: Andrew Gierth In-Reply-To: "Morgan Davis"'s message of "Tue, 24 Aug 1999 12:56:07 -0700" X-Mayan-Date: Long count = 12.19.6.8.10; tzolkin = 9 Oc; haab = 18 Yaxkin X-Pgp-0x0E9FFBE9: 87 25 7F 14 41 24 B3 51 E0 19 8B DE 49 74 0C 29 X-Attribution: AG Date: 24 Aug 1999 21:34:40 +0100 Message-ID: <87d7wc7w9r.fsf@erlenstar.demon.co.uk> Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Morgan" == Morgan Davis writes: Morgan> Perhaps this is a question best suited for David Greenman, Morgan> but I'll ask the -stable collective for feedback. We have a Morgan> 3.2-STABLE news machine, connected to a Network Appliance Morgan> (netApp) RAID. INNd 2.3 (June 11th beta) periodically gets Morgan> stuck in a "vmopar" state. Only fix is a reboot. Looks like Morgan> a VM system issue possibly related to NFS. Any hints or Morgan> confirmation? My small news server repeatedly hangs with innd in "vmpfw", with sometimes another process (e.g. innfeed) hung in "vmopar". Requires a fairly aggressive reboot to fix (any attempt to unmount the news spool filesystem hangs too). This is with FreeBSD-stable as of about June, with local disks and INN 2.2-stable (with every mmap option I could find turned off). Moving to FreeBSD-current isn't really an option. -- Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message