Subject: Re: grouchy tmpfs?
To: None <tech-kern@NetBSD.org>
From: David Young <dyoung@pobox.com>
List: tech-kern
Date: 08/18/2007 15:19:57
On Fri, May 18, 2007 at 08:26:36PM -0500, David Young wrote:
> Today this showed up on the console of one of my machines running -current
> prior to the yamt-idlelwp merge:
> 
> vflushbuf: dirty: tag VT_TMPFS(25) type VBLK(3), usecount 424, writecount 0, refcount 21, flags (000<ONWORKLIST>)
>         tag VT_TMPFS, tmpfs_node 0xc68ba370, flags 0x0, links 1
>         mode 0640, owner 0, group 5, size 0, status 0x0
>  lock type vnlock: EXCL (count 1) by pid 9524.1
> vflushbuf: dirty: tag VT_TMPFS(25) type VBLK(3), usecount 423, writecount 0, refcount 21, flags (000<ONWORKLIST>)
>         tag VT_TMPFS, tmpfs_node 0xc68ba370, flags 0x0, links 1
>         mode 0640, owner 0, group 5, size 0, status 0x0
>  lock type vnlock: EXCL (count 1) by pid 9524.1
> 
> Process 9524, whatever it was, is no longer running.  It did not leave
> a core.

Here is a similar warning.  This is with /dev/ on tmpfs.  This warning
came when I quit with Ctrl-C a script that creates a filesystem with
newfs(8), mounts the filesystem, extracts files onto it with pax(1),
and then umounts.  My script umounts whether I cancel the script with
Ctrl-C or I let the script run to completion.

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933 ext 24