> But today, I started actually _using_ it.  And the kernel started
> blabbering at me about
> 
> nfs_fsync: dirty: type VREG, usecount 2, writecount 1, refcount 2,
> 	tag VT_NFS, fileid 200 fsid 0x2402
> 
> Presumably this is at least somewhat serious, or it wouldn't be
> blatting it all over the console...but it doesn't seem to be crashing
> or anything...anyone know what, if anything, I should be concerned
> about here?

That warning indicates that after the 'guts' of the NFS fsync() vnode
op have been run, there are still blocks on the vnode's dirty block
list.

The reason that that's bad should be obvious.  8-)


chris