2.3 and FreeBSD

N niels at bakker.net
Sun Aug 1 22:37:26 UTC 1999


Quoth Marc Fournier:

>> Not doing anything anymore... 3.2-STABLE from just over a month ago.
>> Marc, did you ever find a solution to the problem?  IIRC you saw exactly
>> the same symptoms. (This time it's a dual PII-400 with 768 MB.)
> After extensive debugging with Matt Dillon, it turns out that pre-4.0
> kernels have a VM fragmentation bug that appears to be the major cause of
> my problem, and which is something that is going to seriously impact
> *anyone* running FreeBSD pre-4.0 kernels...

Ok... I'll contact Matt Dillon then for the exact revisions (looking at
the mailing lists, -current is seriously unstable at the moment,
unfortunately).


> IN my case, the fix: doubled the RAM so that swap is used alot less.

768 MB with no readers, I doubt it has *ever* hit swap. (Well, 6 MB is
swapped out apparently, but the box wedged at a time no crontabs and stuff
were running so expire didn't have a chance to force innd out...)


> A good way of checking to see if this is affecting you is to check the "VM
> pgdata" values in vmstat -m:
> 
>     VM pgdata  1586   352K   9398K128695K    13805    0     0  
> 
> When the 3rd value (9398K) approaches or exceeds the 4th (128695K), expect your system to lock up shortly afterwards...

(Do we have the same versions of vmstat?)

Memory statistics by type                          Type  Kern
        Type  InUse MemUse HighUse  Limit Requests Limit Limit Size(s)
[..]
    VM pgdata   150    23K     23K 40960K      158    0     0  128,256,512

This is after the hang, of course... Did you have any luck tinkering with
PMAP_SHPGPERPROC, by the way?


	-- Niels.



More information about the inn-workers mailing list