Re: ATF t_mlock() babylon5 kernel panics

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Wed, Mar 13, 2019 at 03:22:27PM +0700, Robert Elz wrote:
>   [...]
> 
> netbsd# df /tmp
> Filesystem    1K-blocks       Used      Avail %Cap Mounted on
> tmpfs                 4          4          0 100% /tmp
> 
> That's what it showed (it was still in my xterm scrollback buffer from
> the window I use as the DomU console).    So, no, df isn't showing space
> allocated, just nothing available.   Something had "stolen" all the available
> ram, and wasn't letting go.
> 
> It did not look as if there was no free memory however:
> 
> netbsd# vmstat m
>  procs    memory      page                       disk faults      cpu
>  r b      avm    fre  flt  re  pi   po   fr   sr x0   in   sy  cs us sy id
>  0 0    34868 945956  264   0   0    0    0    0 15  428  426 119  0  0 100
> 
> but something as simple as attempting to read a man page (to check
> what other options I could try):
> 
> netbsd# man vmstat
> man: Formatting manual page...
> mandoc: stdout: No space left on device

I've seen this too. df showed my tmpfs as full (although there
was only a few mb in the 'used' colum) , top was showing a few MB free RAM
but lots of ram allocated to files (I have 8GB RAM). UVM could have 
freed some memory from the file cache for tmpfs ...

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--