Date: 31 Aug 1999 21:08:39 +0100 From: Andrew Gierth <andrew@erlenstar.demon.co.uk> To: The Hermit Hacker <scrappy@hub.org> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: INNd sticks in "vmopar" state Message-ID: <87r9kjhfw8.fsf@erlenstar.demon.co.uk> In-Reply-To: The Hermit Hacker's message of "Wed, 25 Aug 1999 09:16:36 -0300 (ADT)" References: <Pine.BSF.4.10.9908250909340.86612-100000@thelab.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "The" == The Hermit Hacker <scrappy@hub.org> writes:
>> 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.
The> This may not be related, but...
The> When Matt and I investigated my problem with 3.2-STABLE &
The> INN-CURRENT (2.3 wannabe), we narrowed down the problem to a VM
The> fragmentation problem in pre-4.x kernels. Basically, I ran
The> 'vmstat -m' out of cron every 10 minutes, watching for the 'VM
The> pgdata' values closely:
The> VM pgdata 55 16K 211K128695K 73 0 0 128,256,512,2K,256K
The> Basically, once the '211K' value reached the '128695K' value,
The> you were hosed.
This turns out to be unrelated to my problem.
VM pgdata 385 72K 131K 10291K 1522 0 0 128,256,512,1K,2K,4K,16K,32K
# ps axl | grep vmpfw
8 287 1 0 -22 0 16148 5500 vmpfw Ds ?? 242:58.57 /news-spool/
--
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?87r9kjhfw8.fsf>