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

From: Antti Kantee <pooka@cs.hut.fi>
To: Patrick Welche <prlw1@newn.cam.ac.uk>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/30831
Date: Tue, 3 Apr 2007 17:13:03 +0300

 On Tue Apr 03 2007 at 15:02:12 +0100, Patrick Welche wrote:
 > Much better:
 > 
 >               proc   pid     flag nlwps comm
 >                   lwp      flag             wchan
 >         0xcf6f0ce0 24436     4000  2 1         du
 >                 0xcc5f1b00   4         0xceb72f18 (smbwrq)
 
 Right, that's what I was looking for.  And I bet the kernel stack
 backtrace for that lwp would come through smbfs_reclaim() and
 smbfs_inactive().
 
 > and your patch seems to have done the trick! At least, I think I would
 > have had a panic by now without it.
 
 Cool!  Unfortunately, the real issue still remains.  But I'm going to
 close this smb-specific PR now.
 
 > (Unrelated oddity with smbfs mounts: quite a few messages of the form:
 > 
 > du: /some/file/or/other: No such file or directory
 > 
 > when it definitely exists...)
 
 Is that a caching issue?  Or do they exist already at, say, mounttime?
 Can you stat the files?  Is du the only one affected by this?  Is there
 anything in common with the affected files: something in the name
 (e.g. length or special character), file type, file date, full path
 length, full path prefix, parent directory, ....
 
 This is probably a problem in smb, might warrant another PR.
 
 -- 
 Antti Kantee <pooka@iki.fi>                     Of course he runs NetBSD
 http://www.iki.fi/pooka/                          http://www.NetBSD.org/
     "la qualité la plus indispensable du cuisinier est l'exactitude"