Date: 24 Aug 1999 21:34:40 +0100 From: Andrew Gierth <andrew@erlenstar.demon.co.uk> To: freebsd-stable@freebsd.org Subject: Re: INNd sticks in "vmopar" state Message-ID: <87d7wc7w9r.fsf@erlenstar.demon.co.uk> In-Reply-To: "Morgan Davis"'s message of "Tue, 24 Aug 1999 12:56:07 -0700" References: <NCBBKMLBAHBFCCLKDAGLMEFGCJAA.mdavis@cts.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Morgan" == Morgan Davis <mdavis@cts.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87d7wc7w9r.fsf>