On Thu, 24 Jan 2008, Andrew Doran wrote:

>>> vrelel: missing VOP_CLOSE(): vnode @ 0xffff800048f80d80, flags
>>> (30<MPSAFE,LOCKSWORK>)
>>>         tag VT_UFS(1), type VREG(1), usecount 1, writecount 0, holdcount 1
>>>         freelisthd 0x0, mount 0xffff8000045cb000, data 0xffff800048f360f0
>>>         tag VT_UFS, ino 811439, on dev 0, 0 flags 0x11, effnlink 1, nlink 1
>>>         mode 0100444, owner 0, group 0, size 837 lock type vnlock: EXCL
>>>         (count 1) by pid 451.1
>>>
>>
>> Ok, these are just spam and can be ignored. I fixed the assertion so if it
>> fires again should be catching real problems. Although, a missing VOP_CLOSE
>> is likely to be "mostly harmless" and doesn't mean the machine is going down
>> in flames.
>
> sys/kern/vfs_subr.c 1.321

Yup - seems to have gone away.  Thanks for the quick response.

----------------------------------------------------------------------
|   Paul Goyette   | PGP DSS Key fingerprint: |  E-mail addresses:   |
| Customer Service | FA29 0E3B 35AF E8AE 6651 |  paul@whooppee.com   |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette@juniper.net |
----------------------------------------------------------------------