K 10
svn:author
V 4
grog
K 8
svn:date
V 27
2004-10-06T02:06:11.000000Z
K 7
svn:log
V 689
getnewvnode: Weaken the panic "cleaned vnode isn't" to a warning.

  Discussion: this panic (or waning) only occurs when the kernel is
  compiled with INVARIANTS.  Otherwise the problem (which means that
  the vp->v_data field isn't NULL, and represents a coding error and
  possibly a memory leak) is silently ignored by setting it to NULL
  later on.

  Panicking here isn't very helpful: by this time, we can only find
  the symptoms.  The panic occurs long after the reason for "not
  cleaning" has been forgotten; in the case in point, it was the
  result of severe file system corruption which left the v_type field
  set to VBAD.  That issue will be addressed by a separate commit.

END