you're the first one to report this problem.
are you using softdeps?

try unmounting the filesystem (which will probably fail, but that's ok).
the attempt to unmount will flush filesystem data, which might clear
up the problem (and also be mildly informative).

have you picked up my fix to ffs_vfsops.c from yesterday?
that might fix it, but I wouldn't be surprised if it didn't too.

-Chuck


On Sun, Dec 03, 2000 at 05:40:59PM -0500, Lennart Augustsson wrote:
> I'm getting the following DIAGNOSTIC message (ffs_vnops.c, line 420) over
> and over again.  The actual vnode varies from message to message,
> 
> Is it something to worry about?
> 
>     -- Lennart
> 
> ffs_fsync: dirty: tag 1 type VREG, usecount 1, writecount 1, refcount 1,
>         tag VT_UFS, ino 1704257, on dev 0, 4 flags 0x10, effnlink 1, nlink 1
>         mode 0100644, owner 371, group 0, size 2506752 lock type vnlock: EXCL (count 1) by pid 271
>