Re: kern/38265: was: Re: kern/38778: /kern files do not show up anymore after quite some time]

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR kern/38265; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: makoto%ki.nu@localhost
Subject: Re: kern/38265: was: Re: kern/38778: /kern files do not show up
        anymore after quite some time]
Date: Sun, 18 Jan 2009 00:09:22 +0000

 The following didn't make it to gnats. (Things need to be sent to
 gnats-bugs as well as or instead of netbsd-bugs.)
 
 Also, 38778 was closed as a duplicate of 38265.
 
    ------
 
 From: Makoto Fujiwara <makoto%ki.nu@localhost>
 To: netbsd-bugs%netbsd.org@localhost
 Cc: ad%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost
 Subject: Re: kern/38778: /kern files do not show up anymore after quite some
        time
 Date: Wed, 14 Jan 2009 09:59:54 +0900
 
 | On a freshly booted system there is no problems to see files under /kern;
 | after quite some time/use (cvs up src + kerne build), they do not show
 | up anymore but remain available.
 
   This symptom may be triggered intensive file access, and in
 my case rsync -aH /m/NFS-HOST/ /local-dir/ with having
 /m/NFS-HOST at large size. It is really 180GB for here.
 It only needs two minutes to reproduce the problem.
  But just find src -newer tarball.tgz or find src tarball.tgz may
 be the key. 
 
  I have tracked down this problem, and it seems to me
 that the changes in the range of
   2008/01/24 17:30 UTC - 2008/01/24 18:00 UTC
 is the key to this behavior.
 
 Also when I rebooted at 2008-01-24 18:00 kernel, I was getting
 following problem.
    unmounting file systems...panic: unmount: dangling vnode
 
 In this range: following commit seems to be very suspicious:
  http://mail-index.netbsd.org/source-changes/2008/01/24/msg001255.html
 
 Related mail:
  http://mail-index.netbsd.org/current-users/2008/03/25/msg001514.html
 
 Thanks:
 ---
 Makoto Fujiwara,